Simplify HPC and Batch workloads on Azure
Перейти к файлу
Fred Park f9782878f1 Tag for 2.5.3 release 2017-03-01 07:39:00 -08:00
cascade Terminate cascade on thread failures 2016-11-19 10:39:58 -08:00
config_templates Add support for task retention time 2017-01-31 09:40:16 -08:00
convoy Tag for 2.5.3 release 2017-03-01 07:39:00 -08:00
docs Add rebootnode command 2017-02-28 19:37:57 -08:00
recipes Add rebootnode command 2017-02-28 19:37:57 -08:00
resources Azure file dvd support for all supported hosts 2016-08-29 12:12:50 -07:00
scripts Pin blobxfer version and add termtasks option 2017-02-28 09:45:24 -08:00
tfm Fix unencrypted task file mover delimiter issue 2017-01-30 15:06:32 -08:00
.gitattributes Add gettaskfile/getnodefile actions 2016-09-08 20:15:11 -07:00
.gitignore Add AAD X.509 cert auth support (#10) 2017-01-10 11:48:39 -08:00
.travis.yml Fix Docker tmpdir 2017-01-24 14:43:44 -08:00
CHANGELOG.md Tag for 2.5.3 release 2017-03-01 07:39:00 -08:00
CONTRIBUTING.md Add a contributing recipes guide 2016-10-27 12:53:12 -07:00
Dockerfile Minor updates 2016-11-30 12:41:07 -08:00
LICENSE Add dummy README 2016-07-18 08:15:56 -07:00
README.md Add AAD X.509 cert auth support (#10) 2017-01-10 11:48:39 -08:00
install.sh Add envvar support for certain config options 2016-11-28 11:02:09 -08:00
install_conda_windows.cmd Add Anaconda on Windows install script 2016-11-03 11:02:10 -07:00
requirements.txt Add AAD X.509 cert auth support (#10) 2017-01-10 11:48:39 -08:00
shipyard.py Add rebootnode command 2017-02-28 19:37:57 -08:00

README.md

Build Status Docker Pulls Image Layers

Batch Shipyard

Batch Shipyard is a tool to help provision and execute batch-style Docker workloads on Azure Batch compute pools. No experience with the Azure Batch SDK is needed; run your Dockerized tasks with easy-to-understand configuration files!

Major Features

  • Automated Docker Host Engine installation tuned for Azure Batch compute nodes
  • Automated deployment of required Docker images to compute nodes
  • Accelerated Docker image deployment at scale to compute pools consisting of a large number of VMs via private peer-to-peer distribution of Docker images among the compute nodes
  • Comprehensive data movement support: move data easily between locally accessible storage systems, Azure Blob or File Storage, and compute nodes
  • Docker Private Registry support
  • Automatic shared data volume support
  • Seamless integration with Azure Batch job, task and file concepts along with full pass-through of the Azure Batch API to containers executed on compute nodes
  • Support for Azure Batch task dependencies allowing complex processing pipelines and DAGs with Docker containers
  • Transparent support for GPU-accelerated Docker applications on Azure N-Series VM instances
  • Support for multi-instance tasks to accommodate Dockerized MPI and multi-node cluster applications on compute pools with automatic job completion and Docker task termination
  • Transparent assist for running Docker containers utilizing Infiniband/RDMA for MPI on HPC low-latency Azure VM instances:
    • A-Series: STANDARD_A8, STANDARD_A9
    • H-Series: STANDARD_H16R, STANDARD_H16MR
    • N-Series: STANDARD_NC24R (not yet ready with Linux hosts)
  • Automatic setup of SSH users to all nodes in the compute pool and optional tunneling to Docker Hosts on compute nodes
  • Support for credential management through Azure KeyVault

Installation

Installation is typically an easy two-step process. The CLI is also available as a Docker image: alfpark/batch-shipyard:cli-latest. Please see the installation guide for more information regarding installation and requirements.

Documentation

Please refer to the Batch Shipyard Guide for a complete primer on concepts, usage and a quickstart guide.

Please visit the Batch Shipyard Recipes for various sample Docker workloads using Azure Batch and Batch Shipyard after you have completed the introductory sections of the Batch Shipyard Guide.

Batch Shipyard Compute Node OS Support

Batch Shipyard is currently only compatible with Azure Batch supported Marketplace Linux VMs.

Change Log

See the CHANGELOG.md file.


This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.