Projects tagged ‘cloud’ and ‘storage’

CloudBuddy's official website - http://www.mycloudbuddy.com/CloudBuddy is a free bucket explorer platform for Amazon S3. It is developed using .NET 3.0 and C# for Windows XP and Vista. Why an ... [More] another Bucket Explorer ? CloudBuddy is not just a simple bucket explorer tool. It is a platform for people to quickly integrate or build features on top of CloudBuddy. It comes with a rich set of S3 User Interface API which can be integrated seamlessly with any .NET applications. On top of all this, CloudBuddy is a free tool. New Features 1. CloudBuddy Personal has been re-designed from the scratch to provide the same feel of your windows explorer. 2. A plug-in framework that allows developers and product owners/companies to either develop new features or to integrate their existing products within the CloudBuddy platform 3. CloudBuddy supports selective Encryption to secure your files and folder content. You have the option to change the encryption keys at any point in time. It allows you to export/import the keys for mobilizing between various devices. 4. CloudBuddy now has incorporated keyboard shortcuts for operations such as Copy, Delete, Refresh, Help etc. 5. CloudFront Distribution which is a feature to distribute data through a server closest to the user's geographical location 6. More features in MS- Office Basic Features of CloudBuddy 1. Allows you to manage multiple S3 accounts 2. Provides easy to use options to perform S3 related operations such as New bucket and folder creation Remove existing bucket, folders and files. Supports multiple folders and files deletion. Supports asynchronous upload and download of files, folders and bucket. CloudBuddy uses ThreeSharp libraries for upload and download purpose. (http://www.codeplex.com/ThreeSharp) Retry option for failed uploads and downloads. Provides option to copy files from one folder to another. Meta data management Advance Features 1. MS-Office plug-in helps you to manage your documents, workbooks, emails, presentations and project files directly on the s3 cloud. 2. All operations are exposed via CloudBuddy API to integrate with third party applications. 3. Upload and Download is written as a window service using WCF. 3. Event notification is propagated for asynchronous operations such as upload and download. 4. File sharing using templates. Sharing files using S3 is just sending a list of URL's to my contact asking them to click on every link to view or download the content. Just imagine, if there is a way for you to share files using a nice HTML page with some welcome messages. Thats exactly what CloudBuddy Template provides you. Check out the following user manual link to know more about File Sharing Templates. http://www.mycloudbuddy.com/usermanual.html#ShareFiles 5. Access CloudBuddy API using python. Learn more here. 6. Browse Jungle Disk Buckets using CloudBuddy 7. Synchronize your desktop folder to a remote S3 folder. Supports multiple folder synchronization in varied intervals. 8. CloudBuddy caches your uploaded files to minimize your bandwidth usage during download. 9. Simplified Uploads - Supports drag and drop of files and folders. CloudBuddy latest can be downloaded in the following URL. http://cloudbuddy.googlecode.com/files/Cloudbuddy_SetUp_2.0.exe Complete User Documentation is available in the following URL. http://www.mycloudbuddy.com/documentation.html We are currently working on 1. CloudBuddy Template Development Guide - A guide for developers to quickly develop templates to enable S3 users to share files effectively. 2.CloudBuddy Plugin Development Guide - A guide for developers to add features to CloudBuddy Platform. 3. Video and Document sharing Templates - End user templates to share files. 4. CloudBuddy Windows Explorer Plug-in - Plug-in that enables users to manage their uploads and downloads using windows explorer. [Less]

Sector is a system infrastructure software that provides functionality for distributed data storage, access, and analysis/processing. It automatically manages large volumetric data across servers or ... [More] clusters, even those over distributed wide area high speed networks. Sector provides simple tools and APIs to access and/or process the data. Data and server locations are transparent to users, as the whole Sector network is a single networked super computer to the users. [Less]

s3backer is a filesystem that contains a single file backed by the Amazon Simple Storage Service (Amazon S3). As a filesystem, it is very simple: it provides a single normal file having a fixed size. ... [More] Underneath, the file is divided up into blocks, and the content of each block is stored in a unique Amazon S3 object. In other words, what s3backer provides is really more like an S3-backed virtual hard disk device, rather than a filesystem. In typical usage, a normal filesystem is mounted on top of the file exported by the s3backer filesystem using a loopback mount (or disk image mount on Mac OS X). This arrangement has several benefits compared to more complete S3 filesystem implementations: By not attempting to implement a complete filesystem, which is a complex undertaking and difficult to get right, s3backer can stay very lightweight and simple. Only three HTTP operations are used: GET, PUT, and DELETE. All of the experience and knowledge about how to properly implement filesystems that already exists can be reused. By utilizing existing filesystems, you get full UNIX filesystem semantics. Subtle bugs or missing functionality relating to hard links, extended attributes, POSIX locking, etc. are avoided. The gap between normal filesystem semantics and Amazon S3 ``eventual consistency'' is more easily and simply solved when one can interpret S3 objects as simple device blocks rather than filesystem objects (see below). When storing your data on Amazon S3 servers, which are not under your control, the ability to encrypt data becomes a critical issue. s3backer supports secure encryption and authentication. Alternately, the encryption capability built into the Linux loopback device can be used. Since S3 data is accessed over the network, local caching is also very important for performance reasons. Since s3backer presents the equivalent of a virtual hard disk to the kernel, most of the filesystem caching can be done where it should be: in the kernel, via the kernel's page cache. However s3backer also includes its own internal block cache for increased performance, using asynchronous worker threads to take advantage of the parallelism inherent in the network. Consistency GuaranteesAmazon S3 makes relatively weak guarantees relating to the timing and consistency of reads vs. writes (collectively known as "eventual consistency"). s3backer includes logic and configuration parameters to work around these limitations, allowing the user to guarantee consistency to whatever level desired, up to and including 100% detection and avoidance of incorrect data. These are: s3backer enforces a minimum delay between consecutive PUT or DELETE operations on the same block. This ensures that Amazon S3 doesn't receive these operations out of order. s3backer maintains an internal block MD5 checksum cache, which enables automatic detection and rejection of `stale' blocks returned by GET operations. This logic is configured by the following command line options: --md5CacheSize, --md5CacheTime, and --minWriteDelay. Zeroed Block OptimizationAs a simple optimization, s3backer does not store blocks containing all zeroes; instead, they are simply deleted. Conversely, reads of non-existent blocks will contain all zeroes. In other words, the backed file is always maximally sparse. As a result, blocks do not need to be created before being used and no special initialization is necessary when creating a new filesystem. When the --listBlocks flag is given, s3backer will list all existing blocks at startup so it knows ahead of time exactly which blocks are empty. File and Block Size Auto-DetectionAs a convenience, whenever the first block of the backed file is written, s3backer includes as meta-data (in the x-amz-meta-s3backer-filesize header) the total size of the file. Along with the size of the block itself, this value can be checked and/or auto-detected later when the filesystem is remounted, eliminating the need for the --blockSize or --size flags to be explicitly provided and avoiding accidental mis-interpretation of an existing filesystem. Block Caches3backer includes support for an internal block cache to increase performance. The block cache cache is completely separate from the MD5 cache which only stores MD5 checksums transiently and whose sole purpose is to mitigate ``eventual consistency''. The block cache is a traditional cache containing cached data blocks. When full, clean blocks are evicted as necessary in LRU order. Reads of cached blocks will return immediately with no network traffic. Writes to the cache also return immediately and trigger an asynchronous write operation to the network via a separate worker thread. Because the kernel typically writes blocks through FUSE filesystems one at a time, performing writes asynchronously allows s3backer to take advantage of the parallelism inherent in the network, vastly improving write performance. The block cache can be configured to store the cached data in a local file instead of in memory. This permits larger cache sizes and allows s3backer to reload cached data after a restart. Reloaded data is verified via MD5 checksum with Amazon S3 before reuse. The block cache is configured by the following command line options: --blockCacheFile, --blockCacheNoVerify, --blockCacheSize, --blockCacheThreads and --blockCacheWriteDelay. Read Aheads3backer implements a simple read-ahead algorithm in the block cache. When a configurable number of blocks are read in order, block cache worker threads are awoken to begin reading subsequent blocks into the block cache. Read ahead continues as long as the kernel continues reading blocks sequentially. The kernel typically requests blocks one at a time, so having multiple worker threads already reading the next few blocks improves read performance by taking advantage of the parallelism inherent in the network. Note that the kernel implements a read ahead algorithm as well; its behavior should be taken into consideration. By default, s3backer passes the -o max_readahead=0 option to FUSE. Read ahead is configured by the --readAhead and --readAheadTrigger command line options. Encryption and Authentications3backer supports encryption via the --encrypt, --password, and --passwordFile flags. When encryption is enabled, SHA1 HMAC authentication is also automatically enabled, and s3backer rejects any blocks that are not properly encrypted and signed. Encrypting at the s3backer layer is preferable to encrypting at an upper layer (e.g., at the loopback device layer), because if the data s3backer sees is already encrypted it can't optimize away zeroed blocks or do meaningful compression. Read-Only AccessAn Amazon S3 account is not required in order to use s3backer. Of course a filesystem must already exist and have S3 objects with ACL's configured for public read access (see --accessType below); users should perform the looback mount with the read-only flag (see mount(8)) and provide the --readOnly flag to s3backer. This mode of operation facilitates the creation of public, read-only filesystems. Simultaneous MountsAlthough it functions over the network, the s3backer filesystem is not a distributed filesystem and does not support simultaneous read/write mounts. (This is not something you would normally do with a hard-disk partition either.) s3backer does not detect this situation; it is up to the user to ensure that it doesn't happen. Statistics Files3backer populates the filesystem with a human-readable statistics file. See --statsFilename below. LoggingIn normal operation s3backer will log via syslog(3). When run with the -d or -f flags, s3backer will log to standard error. OK, Where to Next?Try it out! No Amazon S3 account is required. See the ManPage for further documentation and the CHANGES file for release notes. Join the s3backer-devel group to participate in discussion and development of s3backer. [Less]

Ulysses Agenda is a web-based MUD set in a futuristic, science fiction world where the only way to survive is to make money - one way or another. The game is built upon Windows Azure and ASP.NET MVC.

The Cloud Storage Library project is made up of a PHP client library that lets you integrate with common APIs that both Amazon S3 and Nirvanix supports. The goal is to create compatible client code ... [More] that can be portable on either cloud storage service. Let us know if you have any questions. dave at plaformd dot com [Less]

Mosso's Cloud Files is a remote storage system which is similar in principle to Amazon's S3. It provides a simple RESTful interface to storing and retrieving objects. ... [More] http://www.mosso.com/cloudfiles.jsp cloudfuse is a simple filesystem implemented with FUSE which provides access to Cloud Files. It is still quite rough, but should improve with time and use. [Less]

ClouderaCMS is an CMS web application which uses ASP.NET and Windows Azure.

The Open Cloud Consortium (OCC):Supports the development of standards for cloud computing and frameworks for inter-operating between clouds; develops benchmarks for cloud computing; supports reference ... [More] implementations for cloud computing, preferably open source reference implementations; manages a testbed for cloud computing called the Open Cloud Testbed; sponsors workshops and other events related to cloud computing. Large Data Cloud Interoperability This site discusses various open source projects intended to support interoperability between large data clouds. These projects include: Sector JNI A Java Native Interface / NIO interface to the Sector C++ client API, allowing Java clients to access the Sector distributed file system. PySector A Python extension to the Sector C++ client, allowing Python clients to access the Sector distributed file system. PySphere A Python embedding of the Sector / Sphere MapReduce framework. SectorFileSystem An implementation of the Hadoop File System abstraction which allows Hadoop MapReduce applications to be executed against data stored in the Sector distributed file system. ThriftStore A Thrift based service providing a common interface over multiple cloud storage systems. Detailed information can be found at ComponentsOverview [Less]

EffiProz is a pure C# database that can be easily deployed in cloud, standalone & embedded configurations.

JAzure is a Java library that provides access to the Microsoft Windows Azure Storage Services API.