[osol-discuss] Re: Project Proposal: SAM-QFS
[EMAIL PROTECTED] wrote: smake, star, sformat, sfind (a bit newer), I think it is better to rename such tools to schillymake, schillytar, schillyformat or put them into usr/schilly/bin. or even better simply to make, tar, format, ... Afterall they are only an implementation of these well specified and long existing programs. Credits to Jörg that they may be the best implementation on earth, but I really see no advantage in having Schilly's 's' in the name just to honor his work. I find it much more interesting that SAM-FS/QFS might go open source than reading this years old discussion. Nobody before got his or her name in the Solaris filesystem who has implemented more complex stuff and with more creative ideas than Jörg, who obviously has just the goal of getting his name there... - Thomas This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Project Proposal: SAM-QFS
On 15/06/07, Thomas Maier-Komor [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: smake, star, sformat, sfind (a bit newer), I think it is better to rename such tools to schillymake, schillytar, schillyformat or put them into usr/schilly/bin. or even better simply to make, tar, format, ... Afterall they are only an implementation of these well specified and long existing programs. Credits to Jörg that they may be the best implementation on earth, but I really see no advantage in having Schilly's 's' in the name just to honor his work. The s should remain if only because that has been the names of those programs far longer than some people have been alive :) -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Project Proposal: SAM-QFS
Shawn Walker [EMAIL PROTECTED] wrote: or even better simply to make, tar, format, ... Afterall they are only an implementation of these well specified and long existing programs. Credits to Jörg that they may be the best implementation on earth, but I really see no advantage in having Schilly's 's' in the name just to honor his work. The s should remain if only because that has been the names of those programs far longer than some people have been alive :) Well I remember an anecdote in 1986 at Berthold AG where someone called sed and did not know how to escape. He shouted sh** 'Schily editor', I cannot escape from it ;-) Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Project Proposal: SAM-QFS
Thanks, Ted. You have seconds, and the Storage Community Group confirmed sponsorship. I'll contact you offline to get you set up. Eric On Tue, 24 Apr 2007, Ted Pogue wrote: Project Overview: I propose the creation of a project on opensolaris.org, to bring to the community Solaris host-based data services; namely the Storage Archive Manager or SAM and the Solaris shared file system QFS. These data services exist today and are distributed commercially by Sun as the Sun StorageTek Storage Archive Manager and Sun StorageTek QFS shared file system. The software is delivered unbundled commercially for Solaris 9 and 10, but also is compiled for and runs on Open Solaris. Project Description: Although SAM/QFS are positioned and marketed as two separate data services, they are really a single code base. SAM is the Storage Archive Manager component and consists of a policy based HSM. QFS is a shared or cluster file system for Solaris, and supports shared QFS Linux clients. The QFS shared file system is a high-performance, 64-bit Solaris file system. This file system ensures that data is available at device-rated speeds when requested by one or more users. The QFS shared file system supports from 1 to 128 compute nodes to allow file sharing to scale with computational needs. QFS is ideally suited for Oracle RAC users and applications with a streaming I/O profile SAM is tightly integrated with QFS, and adds the features of a storage archive manager to QFS. A SAM-QFS file system configuration allows data to be archived to and retrieved from local or remote automated tape libraries or disk at device-rated speeds. SAM manages QFS data online, nearline, and offline automatically and in a manner that is transparent to the user or application. Users read and write files to a SAM-QFS file system as though all files were on primary storage. In addition, SAM protects QFS file system data continually, automatically, and unobtrusively. Multiple file copies can be made to many media types and storage tiers in a standard OPEN format. This minimizes the requirement for traditional back-up only and provides fast disaster recovery in an effective long-term data storage solution. A SAM-QFS file system configuration is especially suited to data-intensive applications that require a scalable and flexible storage solution, superior data protection, and fast disaster recovery. This solution also includes an integrated non-mirroring volume manager for performance, automated and flexible policy management, and browser-based management tools. Community Involvement: By open sourcing SAM and QFS software, we will enhance OpenSolaris as a storage platform. Those that adopt OpenSolaris will benefit from an open storage platform, while providing valuable feedback to the commercially distributed software sold and supported by Sun. We plan to develop our next release of SAM/QFS in the Open Source community, so we invite community feedback on our work in progress. We intend to make periodic (every few weeks) code drops to the project page for download by the community. The longer term strategy will be to migrate from CVS to Mercurial as a source control tool and make the repository part of the open source project. This will allow the community to comment on features and our code base as we work through the development phase of the next and future commercial releases of this software.Additionally, it will allow for community contributions. A complete set of the Sun StorageTek SAM and Sun StorageTek QFS administration guides can be found at: http://docs.sun.com/app/docs/coll/QFS4_6 http://docs.sun.com/app/docs/coll/SAM4_6 Community Leaders: Svati Chandra Narula Ted Pogue Harriet Coverston Cindy Dyrness SAM/QFS - New Solaris Storage Group ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Project Proposal: SAM-QFS
Project Description: ... The QFS shared file system is a high-performance, 64-bit Solaris file system. This file system ensures that data is available at device-rated speeds when requested by one or more users. The QFS shared file system supports from 1 to 128 compute nodes to allow file sharing to scale with computational needs. QFS is ideally suited for Oracle RAC users and applications with a streaming I/O profile Second that. If this gets approved as a project... wow, wow, wooow! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Project Proposal: SAM-QFS
I did research about 5 years ago regarding HSM file systems. QFS/SAMFS was a leading contender in that space. It also had the added benefit of having a truly massive ability to scale. (We ended up going with another product, because our first choice of optical jukeboxes was not supported.) This is truly great news for the both the OpenSolaris and the greater FOSS communities. This should definitely be a supported project. As far as file naming conventions go, we may want to wait to make any decisions until a project is approved. That said, I'd say my first preference would be to give precedence to projects that are going into Solaris Express (unless there are truly mitigating circumstances). Ideally the project team would re-factor QSAM-FS to allow installation in a user specified location. Other improvements would deal with installation and configuration ease. I'd also really like to see the large scale clustering capabilities of QSAMFS brought to ZFS. Wouldn't it be cool if you could have a cluster meta zpool, so that any host in your data center could be configured to painlessly allow file system growth from a a shared storage pool? Might as well bring HSM to ZFS while we are at it. ;) -brian This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Project Proposal: SAM-QFS
Is there a plan to incorporate this into Solaris Express? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Project Proposal: SAM-QFS
community groups - would it be fair to assume this project will be affiliated with the existing Storage community? I have been told that there is going to be a new file system community soon. This seems to be the ideal fit. -brian This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
