Refactoring is a strategic undertaking whose value is only realized in the fullness of time. In the case of refactored Univa Unisight, however, an agile approach is allowing us to deliver an impressive cadence of multiple releases per year – and with each release, significantly enhanced capabilities.
Enhancements to our Rules Engine, in just-released Univa Unisight 4.3, provides for a compelling illustration. Up to and including Univa Unisight 4.1, a rules-engine capability of any kind was notably absent. Then about 5 months ago, with the release of version 4.2, a rules-based alerting capability was introduced. Though many of us alluded to this enhancement only in the most modest of terms, it proved to be more than just a milestone on the path to ‘something even better’. For example, using this capability in Unisight 4.2, it took me literally seconds to illustrate that jobs in an “Eqw” state could readily trigger an alert (e.g., display a notification in the Unisight WebUI, send an email, or execute a script) for those admins responsible for Univa Grid Engine.
With the recent release of Univa Unisight 4.3, however, our Rules Engine has been extended well beyond just alerting. Specifically, with this latest release, data known to Unisight can be framed as a variable. For example, with this latest release jobs in an “Eqw” state could trigger a specific and therefore useful alert – more specific and useful because data known to Unisight (e.g., user, job ID and state, plus queue) have been passed to the email handler as variables. Of course, such variables could be passed alternatively for the purpose of display (within the Unisight WebUI), to another rule (i.e., “rule chaining”), or to an involved script. The enhancement is rich and robust enough that it is already being used to automate preemptive scheduling capabilities – a natural augmentation of the manual preemption capability we introduced in version 8.3 of Univa Grid Engine some time ago …
Obviously, we’re quite excited with the possibilities the enhanced Rules Engine introduces as of the version 4.3 release. However, we fully expect our customers to ultimately demonstrate the value of this capability as they adopt it in their environments with workload managed by Univa Grid Engine.
Rules aside, there’s even more in this release of Univa Unisight that truly underscores the value of a monitoring and reporting solution targeted expressly for workloads managed via Univa Grid Engine; for example:
Univa Unisight is included with an existing license for Univa Grid Engine. This means our supported customers can easily introduce leading-edge monitoring and reporting capabilities into their environment via a brand-new deployment or through an upgrade.
Although we’ll be making the version 4.3 capabilities of Univa Unisight the focal point of our upcoming webinar, we’ll also spend some time framing visibility into your workload-managed infrastructure from more-generic perspectives. We hope we can look forward to seeing you at this webinar, and/or discussing your monitoring and reporting needs for your HPC and Big Data Analytics infrastructures in the way that works best for you – in person, at SC17 perhaps?