Nirvana (software)

Nirvana

Developer(s)	General Atomics
Initial release	August 8, 2003 (2003-08-08)
Stable release	5.0 / September 15, 2016 (2016-09-15)
Preview release	5.1 / September 15, 2016 (2016-09-15)
Written in	C
Operating system	Linux, Microsoft Windows, OS X, Solaris (operating system)
Platform	X86-64, POWER8, SPARC
Type	Metadata and data management software
License	Proprietary commercial software
Website	www.ga.com/nirvana

Nirvana was virtual object storage software developed and maintained by General Atomics.

It can also be described as metadata, data placement and data management software that lets organizations manage unstructured data on multiple storage devices located anywhere in the world in order to orchestrate global data intensive workflows, and search for and locate data no matter where it is located or when it was created. Nirvana does this by capturing system and user-defined metadata to enable detailed search and enact policies to control data movement and protection. Nirvana also maintains data provenance, audit, security and access control.

Nirvana can reduce storage costs by identifying data to be moved to lower cost storage and data that no longer needs to be stored.

History

Nirvana is the result of research started in 1995 at the San Diego Supercomputer Center (SDSC) (which was founded by and run at the time by General Atomics), in response to a DARPA sponsored project for a Massive Data Analysis System. Led by General Atomics computational plasma physicist Dr. Reagan Moore, development continued through the cooperative efforts of General Atomics and the SDSC on the Storage Resource Broker (SRB), with the support of the National Science Foundation (NSF). SRB 1.1 was delivered in 1998, demonstrating a logical distributed file system with a single Global Namespace across geographically distributed storage systems.

In 2003, General Atomics turned over operation of the SDSC to the University of California San Diego (UCSD) and Dr. Moore became a full-time professor there establishing the Data Intensive Computing Environments (DICE) Center, continuing development of SRB. In that same year, General Atomics acquired the exclusive license to develop a commercial version of SRB, calling it Nirvana. The DICE team ended development of SRB in 2006 and started a rules oriented data management project called iRODS for open source distribution. Dr. Moore and his DICE team relocated to the University of North Carolina at Chapel Hill where iRODS is now maintained by the iRODS Consortium. General Atomics continued development of Nirvana at their San Diego headquarters, focusing on capabilities to serve government and commercial users, including high scalability, fail-over, performance, implementation, maintenance and support.

Nirvana History

In 2009, General Atomics won a data management contract with the US Department of Defense (DOD) High Performance Computing Modernization Program. The requirements of this contract focused General Atomics to expand Nirvana’s performance, scalability, security and ease of use. A major deliverable involved integrating Nirvana with Oracle Corporation's SAM-QFS filesystem to provide a policy-based Hierarchical Storage Management (HSM) system with near real-time event synchronization. General Atomics also announced that digital marketing firm infoGROUP deployed Nirvana to create a Global Name Space across three of infoGROUP’s computer operations centers in the Omaha area.

In 2012, General Atomics released Nirvana version 4.3.

In 2014, General Atomics changed the Nirvana business model from a large government contract, fee for service model, to a standard commercial software model.

In 2015, General Atomics initiated a strategic relationship with pixitmedia/arcastream in the United Kingdom, integrating Nirvana with pixitmedia and arcastream’s products.

In 2016, General Atomics released Nirvana version 5.0.

In May 2018, probes of Nirvana marketing and support URLs under the General Atomics corporate umbrella (www.Nirvanastorage.com, www.ga.com/nirvana and https://www.nirvanaware.com) and more recently branded integration offerings such as "Nirvana EasyHSM" (www.ga.com/easyhsm (mentioned in a Jan. 2017 marketing slideshare at )) return "cannot be found" from www.ga.com or connection timeout. A "Nirvana" keyword search at www.ga.com returns only pages with archived indications. Nirvana pages and press releases archived by General Atomics are retrievable via http://www.ga.com/?Key=Search&q=nirvana

Architecture and operation

Nirvana is client-server software composed of Location Agents that reside on, or access, Storage Resources. A Storage Resource can be a networked-attached storage (NAS) system, object storage system or cloud storage service. Nirvana catalogs the location of the files and objects in these storage resources into its Metadata Catalog (MCAT) and tags the files with storage system metadata (Owner, File Name, File Size and Creation, Change, Modification and Access Timestamps) and additional user-defined, domain specific metadata. System and user-defined metadata can be used to search for a file or object (or groups of files and objects) and also control access to and move those files and objects from one storage resource to another. The MCAT creates a single Global Namespace across all Storage Resources connected to it so users and administrators can search for, access, and move data across multiple heterogeneous storage systems from multiple vendors across geographically dispersed data centers. The MCAT is connected to and interacts with a relational database management system to support its operation. Multiple MCATs can be deployed for horizontal scale-out and failover. Various Clients can interact with Nirvana including the supplied Web browser and Java based GUI Clients, a Command Line Interface, a native Windows virtual network drive interface, and user-developed applications via supplied APIs.

Nirvana Architecture

Nirvana operation is controlled by three daemons; Metadata, Sync and ILM. The Metadata Daemon can extract metadata automatically from an instrument creating data, from within the file's actual data using predefined and customizable templates and metadata parsing policies, or capturing user input via the GUI or Command Line Interface. The Sync Daemon, running in the background, detects when files are added to, or deleted from, the underlying Storage Resource filesystems. When filesystem changes are observed by the Sync Daemon, the changes are registered and updated in MCAT. The ILM Daemon routinely queries the MCAT and executes actions including migration, replication, or backup on a specified schedule. For example, an administrator can set a policy to free up space on an expensive primary storage system by migrating that data to distributed retention locations based on criteria such as: storage consumption watermarks (percent full), all data associated with a specific project, or data that hasn't been accessed in over one year. The policies are extremely flexible. User-defined metadata attributes (e.g. Project, Principal investigator, Data source, Location, Temperature, etc.) can also be used to move data. Nirvana ILM policy execution occurs behind the scenes, transparent to end-users or applications.

Use cases

Data-aware cloud storage gateway

Nirvana's ILM functionality can be used as a cloud storage gateway, where data stored locally, on premises, can be moved to popular cloud storage services based on Nirvana's various metadata attributes and policies. In 2015, General Atomics and ArcaStream announced a cloud storage appliance that uses IBM's Spectrum Scale for on premises storage and integrates with cloud storage providers Amazon S3, and Google Cloud Storage.

Advanced search

Nirvana can be used to conduct search queries to find data of interest using both system and user-defined metadata. Queries are either entered in the Command Line Interface or through the Web browser client shown below.

Nirvana Web Browser Graphical User Interface

Virtual collections

Nirvana can automate the grouping and distribution of data files into a virtual collection - based on user-friendly logical rules. For example, user-defined metadata can be used to identify data files needing to be transferred between collaborators with domain-specific attributes (experiment, study, project, etc.).

Data provenance

In many fields, it is helpful to know the provenance and processing pipeline used to produce derived results. Nirvana tracks data within workflows, through all transformations, analyses, and interpretations. With Nirvana, data can be shared and used with verified provenance of the conditions under which it was generated – so results are reproducible and analyzable for defects.

Audit

Nirvana can be used to audit every transaction on a data file within a workflow. An audit trail can be stored containing information such as date of transaction, success or error code, user performing transaction, type of transaction and notes, etc. Audit trails, like everything else with Nirvana, can be easily queried and filtered.

Security and access control

Nirvana can be used to control access to data by setting up specific access control lists by user, group etc. using user-defined metadata attributes (Project, Study, etc.) and by setting access privilege levels where users assigned higher levels can see more information than others assigned lower levels. Nirvana supports single sign-on and access by integrating with the Lightweight Directory Access Protocol (LDAP) and Active Directory, using challenge–response authentication, Grid Security Infrastructure (GSI), and Kerberos. Data can only be viewed and modified by users authorized to do so.

File system analysis

Nirvana can be used to analyze the makeup of a shared filesystem to determine what type of data is being stored, how much space it takes up, when it was last accessed, and who stored it. With this information, storage administrators can determine the most appropriate type of storage system to use and when to move unused data to lower cost archive storage. In the example below, Nirvana's analysis of data stored on an expensive enterprise NAS storage system showed most data hadn't been accessed in over 2 years. The analysis further showed that most files were very small, and over half the storage was consumed by just two users. Using this data, the organization replaced their enterprise storage system with less expensive object storage to better manage the many small, seldom accessed, files.

Nirvana File Analysis