Академический Документы
Профессиональный Документы
Культура Документы
Omneon CONFIDENTIAL
MediaGrid Overview
What is a MediaGrid?
Active Disk Storage System High Performance Shared Storage Designed for large file storage and access
Typical Usage
RealReal-Time Servers
Ingest
SDI
Playout
SDI
Archive
Browse
Edit
ContentServers
GigE Network
GigE Network
Spectrum ContentServers
MAC Client
ContentBridge Linux
ContentDirectors SystemManager
ContentServers
Linux Client
ContentBridge
ContentManager
ContentDirectors
SystemManager
ContentServers
ContentBridge
MAC Client
ContentManager
ContentDirectors SystemManager
MAC Client
ContentManager
ContentDirectors SystemManager
ContentServers
Linux Client
ContentBridge
MAC Client
ContentManager
ContentDirectors SystemManager
(File Transfer Protocol) (Common Internet Filesystem) (Apple Filing Protocol) (Network File System)
MAC Client Linux Client
ContentServers
ContentBridge
ContentManager
Write Operation
Clients
Metadata
ContentDirectors define ContentDirectors (File System) namespace and provide clients with pointers to the actual data, which typically resides on several ContentServers
GigE Network
2 5 1 4
ContentServers
Content File 1
Content is chopped into slices and stored across multiple ContentServers. Slices are replicated on more than one ContentServer for protection. No RAID.
Read Operation
Clients
Metadata
ContentDirectors define ContentDirectors (File System) namespace and provide clients with pointers to the actual data, which typically resides on several ContentServers
2 5
GigE Network
2 5
1 4 1 3 4
ContentServers
Clients ask ContentDirectors for pointers, then interact directly with ContentServers to access file slices. No NAS head involved in data transferno bottlenecks All interconnect via Ethernetno SAN complexity
ContentDirectors define ContentDirectors (File System) namespace and provide clients with pointers to the actual data, which typically resides on several ContentServers
2 5
GigE Network
2 5
1 4 1 3 4
ContentServers
Access bandwidth scales with number of ContentServers and replication factor Simultaneous file operations are distributed across all ContentServers which have relevant content Each ContentServer operates independently and directly with clients to satisfy access requirements
ContentDirectors define ContentDirectors (File System) namespace and provide clients with pointers to the actual data, which typically resides on several ContentServers
3 3
2 5
GigE Network
2 5
1 4 1 3 4 2
ContentServers
Lost drives or ContentServers do not necessitate a volume rebuild, as in RAID The ContentDirector initiates creation of additional copies of missing file segments in parallel across all ContentServers When a ContentServer or drive is replaced, it appears as new storage to be utilized in the system
ContentServer 1
3-Slice file 1st Copy 3Same 3-Slice file 2nd Copy
ContentServer 2
ContentServer 3
If ContentServer 1 fails, get slice 1 from ContentServer 3, slices 2 & 3 from ContentServer 2 If ContentServer 2 fails, get slices 1 & 2 from ContentServer 1, slice 3 from ContentServer 3 If ContentServer 3 fails, get slices 1 & 2 from ContentServer 1, slice 3 from ContentServer 2.
Load Balancing
Simultaneous Requests 2 Clients Request Same File
Client 1 gets slices 1 & 2 from ContentServer 1
ContentServer 1
3-Slice file 1st Copy Same 3-Slice file 32nd Copy
ContentServer 2
ContentServer 3
Copy 1, Slice 1
Copy 1, Slice 2
Copy 1, Slice 3
Copy 2, Slice 2
Copy 2, Slice 3
Copy 2, Slice 1
Note that the default replication factor is 3 which means 3 copies of the file will be created.
The End