[osol-discuss] SAM-QFS Open Sourced

2008-03-17 Thread Ted Pogue
We are please to announce that we have open sourced the SAM-QFS code!
This major contribution to the OpenSolaris community is available on 
http://opensolaris.org/os/project/samqfs,
with additional information at http://blogs.sun.com/samqfs. We are very 
excited to take this big step in
creating an open source community around SAM-QFS and continuing to grow 
Open Solaris as a premier storage OS.

Regards,
Ted
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] Project Proposal: SAM-QFS

2007-04-25 Thread Ted Pogue

Joerg,
   The SAM commands came out of former LSC, inc. I can't comment on 
what was considered
in the naming of them. I have been with the product in one form or 
another since 1998 and these SAM
commands existed then, probably since 94 or 95. They are included in  
/opt/SUNWsamfs/sbin and bin.

Ted


Joerg Schilling wrote:

Tom Haynes [EMAIL PROTECTED] wrote:

  

While doing this is a really good idea, I see potential name conflicts
with older softare.

Since 20..25 years, I create and publish programs like:

smake, star, sformat, sfind (a bit newer), 

and I recently got some information that SAMFS may include progran names
like star and sfind.

I support this project, but I would like to see that the programs are renamed 
into something like: 'sam*' in order to avoid confusion.


Jörg

  
  
Considering these are currently unbundled and shipping products, that 
might be hard. I.e., would you want to tell
customers that they need to learn new commands, change all of their 
scripts, etc?




Thomas, I am waiting for a reply

Please tell me where potential name clashes are and how you like to 
deal with a problem that seems to be caused by not looking to the outside...


-   Which programs from SAM FS have name clashes?

-   What do you intend to do in order to solve the problem

	-	Do you like to install the SAM FS utilities in 
		directories other than /usr/bin and inform your

customers about possible problems?

-   Do you intend to rename your utilities that
have name clashes?



Jörg

  

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


[osol-discuss] Project Proposal: SAM-QFS

2007-04-24 Thread Ted Pogue


   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


Re: [osol-discuss] Project Proposal: SAM-QFS

2007-04-24 Thread Ted Pogue

All,
I can affiliate with the storage community until an FS community exists 
if that works
for everyone. Oversight on my part not to have included this as part of 
the proposal.

Thanks for the feedback,
Ted


Alan Coopersmith wrote:

Alan DuBoff wrote:
What if you just make it a condition that Ted needs to get the 
affiliation? 


Tom Haynes said this has happened, so I'm satisfied.

If it's just a formality that Ted didn't get an affiliation from an 
existing community, I would affiliate with the Device Driver 
community, which filesystems stradle on. 


Except that the Device Driver community is defunct, having no 
contributors
nor core contributors able to participate in community decision 
making, and
as noted, it's really a better fit for Storage or the proposed File 
Systems

community than Device Drivers anyway.


Is that draft you mention going to have an ETA soon? (i.e., decision)


It's on the agenda for tomorrow's OGB meeting, and as everyone on 
ogb-discuss

seems to have agreed with it, I imagine it will be adopted then.


___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org