Content deleted Content added
m tweaks to bolding in opening sentence |
m task, replaced: IEEE Transaction → IEEE Transactions (3), IEEE Transactionss → IEEE Transactions (2) |
||
| (One intermediate revision by one other user not shown) | |||
Line 1:
{{primary sources|article|date=March 2009}}
Line 6 ⟶ 5:
== Description ==
GOS was a successor of the term [[network-attached storage]] (NAS). GOS systems contained hard disks, often [[RAID]]s (redundant arrays of independent disks), like traditional file servers.
[[Image:gosongrid.jpg |thumb
GOS was designed to deal with long-distance, cross-___domain and single-image file operations, which is typical in Grid environments. GOS behaves like a file server via the file-based GOS-FS protocol to any entity on the grid. Similar to [[Advanced Resource Connector|GridFTP]], GOS-FS integrates a parallel stream engine and [[Grid Security Infrastructure]] (GSI).
Conforming to the universal VFS (Virtual Filesystem Switch), GOS-FS can be pervasively used as an underlying platform to best utilize the increased transfer bandwidth and accelerate the [[Network File System (protocol)|NFS]]/[[CIFS]]-based applications. GOS can also run over [[SCSI]], [[Fibre Channel]] or [[iSCSI]], which does not affect the acceleration performance, offering both file level protocols and block level protocols for [[storage area network]] (SAN) from the same system.
In a grid infrastructure, resources may be geographically distant from each other, produced by differing manufacturers, and have differing access control policies. This makes access to grid resources dynamic and conditional upon local constraints. Centralized management techniques for these resources are limited in their scalability both in terms of execution efficiency and fault tolerance. Provision of services across such platforms requires a distributed resource management mechanism and the peer-to-peer clustered GOS appliances allow a single storage image to continue to expand, even if a single GOS appliance reaches its capacity limitations. The cluster shares a common, aggregate presentation of the data stored on all participating GOS appliances. Each GOS appliance manages its own internal storage space. The major benefit of this aggregation is that clustered GOS storage can be accessed by users as a single mount point.
GOS products fit the thin-server categorization. Compared with traditional “fat server”-based storage architectures, thin-server GOS appliances deliver numerous advantages, such as the alleviation of potential network/grid bottle-necks, CPU and OS optimized for I/O only, ease of installation, remote management and minimal maintenance, low cost and Plug and Play, etc. Examples of similar innovations include NAS, printers, fax machines, routers and switches.
Line 30 ⟶ 29:
==Further reading==
* Frank Wang, Na Helian, Sining Wu, Yuhui Deng, Yike Guo, Steve Thompson, Ian Johnson, Dave Milward & Robert Maddock, Grid-Oriented Storage, IEEE Distributed Systems Online, Volume 6, Issue 9, Sept. 2005.
* Frank Wang, Sining Wu, Na Helian, Andy Parker, Yike Guo, Yuhui Deng, Vineet Khare, Grid-oriented Storage: A Single-Image, Cross-Domain, High-Bandwidth Architecture, IEEE
* Frank Zhigang Wang, Sining Wu, Na Helian, An Underlying Data-Transporting Protocol for Accelerating Web Communications, International Journal of Computer Networks, Elsevier, 2007.
* Frank Zhigang Wang, Sining Wu, Na Helian, Yuhui Deng, Vineet Khare, Chris Thompson and Michael Parker, Grid-based Data Access to Nucleotide Sequence Database with 6x Improvement in Response Times, New Generation Computing, No.2, Vol.25, 2007.
| |||