Website www.univa.com/products | Operating system | |
Stable release 8.4.4 / 9 November 2016; 4 months ago (2016-11-09) License | ||
Univa Grid Engine is a batch-queuing system, forked from Sun Grid Engine (SGE). The software schedules resources in a data center and applies policy management tools. The product can be deployed to run on-premise, using cloud computing or in a hybrid cloud environment.
Contents
History
The roots of Grid Engine as a commercial product date back to 1993 (under the names CODINE and later, in a variation of the product, GRD). A more comprehensive genealogy of the product is described in Sun Grid Engine. Grid Engine was first distributed by Genias Software and from 1999, after a company merger, by Gridware In. In 2000, Sun Microsystems acquired Gridware, Inc. Sun renamed CODINE/GRD as Sun Grid Engine later that year, and released it as open source in 2001.
In 2010, Oracle Corporation acquired Sun and thus renamed SGE to Oracle Grid Engine. The Oracle Grid Engine 6.2u6 source code was not included with the binaries, and changes were not put back to the project's source repository. In response to this, the Grid Engine community started the Open Grid Scheduler and the Son of Grid Engine projects to continue to develop and maintain a free implementation of Grid Engine.
On January 18, 2011, Univa announced that it had hired the principal engineers from the Sun Grid Engine team. Univa Grid Engine development is led by CTO Fritz Ferstl, who founded the Grid Engine project and ran the business within Sun/Oracle for the past 10 years.
On October 22, 2013 Univa announced that it had acquired Oracle Grid Engine assets and intellectual property making it the sole commercial provider of Grid Engine software.
Releases
Univa Grid Engine 8.0 was the first version, released on April 12, 2011. It was forked from SGE 6.2u5, the last open source release. It adds improved third party application integration, license and policy management, enhanced support for software and hardware platforms, and cloud management tools.
Univa Grid Engine 8.0.1 was released on October 4, 2011. It adds improved support for multi-core hardware, integration with NVIDIA GPUs, new job submission verifier extensions, and additional bug fixes.
Univa Grid Engine 8.1.0 has been announced on May 2 and has updated it to the latest release level 8.1.3 in Nov 15 2012. The 8.1.x releases deliver important new functionality such as Job Classes, PostGres Spooling, Resource Maps, Fair Urgency, deterministic Wildcard PE Selection, improved Diagnostics, pre-configured MPI integations and improved Apache Hadoop Integration as well as many bug fixes and performance improvements.
Univa Grid Engine 8.1.6 has been announced on Oct 14, 2013. The update include improvements to the Grid Engine scheduler for larger clusters and Qmaster stability improvements for spooling and qalter commands.
Univa Grid Engine 8.2.0 was released on Sept 02, 2014. The new Univa Grid Engine version 8.2 includes native Windows support .
Univa Grid Engine 8.3.0 was released on June 22, 2015. The new Preemption feature in Univa Grid Engine 8.3.0 allows users to set priorities on different work so that, if a higher priority application must use resources currently allocated to a lower priority application, the lower priority application will effectively be “paused” -- not lost -- and work will automatically resume once the higher priority application is completed. Among a handful of other new features added to Grid Engine 8.3.0 to improve the overall reliability and efficiency of the cluster, is the new Run Time Modification of Resources feature. The Run Time Modification of Resources feature means much more efficient use of cluster resources.
Univa Grid Engine 8.3.1 was released on August 28, 2015. This release contained all of the new features in Univa Grid Engine 8.3.0 and additional fixes and enhancements identified since the release of 8.3.0.
Univa Grid Engine 8.4.0 was released on May 31, 2016. This release supports Docker containers and will automatically dispatch and run jobs with a user specified Docker Image.