Bright Computing Steps up with Cloud Bursting to Azure at ISC 2017

Print Friendly, PDF & Email

Bill Wagner, CEO, Bright Computing

In this video from ISC 2017, Bill Wagner from Bright Computing describes the company’s new capabilities for Cloud Bursting to Microsoft Azure.

“Cloud bursting from an on-premises cluster to Microsoft Azure offers companies an efficient, cost-effective, secure and flexible way to add additional resources to their HPC infrastructure. Bright’s integration with Azure also gives our clients the ability to build an entire off-premises cluster for compute-intensive workloads in the Azure cloud platform.”

The Bright integration with Azure enables organizations to provision and manage virtual servers running on the Azure cloud platform, as if they were local machines. Organizations can use this feature to build an entire cluster in Azure from scratch, or extend an on-premises cluster into the Azure cloud platform when extra capacity is needed.

Key features of the Bright Cluster Manager 8.0 integration with Azure include:

  • Uniformity – Bright Cluster Manager 8.0 ensures that cloud nodes look and feel exactly like on-premises nodes. This is accomplished by using the same software images to provision cloud nodes, as the software images that are already being used to provision on-premises nodes. Users are authenticated on cloud nodes in the same way as on-premises nodes, providing a seamless administration experience. A single workload setup allows users to manage separate queues for on-premises and cloud nodes.
  • Streamlined setup process – An intuitive wizard in Bright View asks some simple questions to quickly and easily set up the cloud bursting environment. In addition, Azure API endpoints are accessed via a single outgoing VPN port in the internet.
  • Data management – Bright Cluster Manager 8.0 includes a tool which automatically moves job data in and out of Azure.
  • Scale – Bright allows organizations to scale nodes up and down, based on the workload. Virtual nodes in the cloud can be terminated automatically when they are no longer needed, and recreated when new jobs are submitted to the queue.

See our complete coverage of ISC 2017

Sign up for our insideHPC Newsletter