5.2 KiB
5.2 KiB
Change Log
Unreleased
Added
- Comprehensive data movement support. Please see the configuration doc for
more information.
- Ingress from local machine with
files
in global configuration- To GlusterFS shared volume
- To Azure Blob Storage
- To Azure File Storage
- Ingress from Azure Blob or File Storage with
input_data
in pool and jobs configuration- Pool-level: to compute nodes
- Job-level: to compute nodes prior to running the specified job
- Task-level: to compute nodes prior to running a task of a job
- Egress to local machine as actions
- Single file from compute node
- Entire task-level directories from compute node
- Egress to Azure Blob of File Storage with
output_data
in jobs configuration- Task-level: to Azure Blob or File Storage on succesful completion of a task
- Ingress from local machine with
- Experimental support for OpenSSH with HPN patches on Ubuntu
- Additional actions:
ingressdata
,gettaskallfiles
,listjobs
,listtasks
. Please see the usage doc for more information. - Data movement overview and guide doc
- Torch-CPU as an option in quickstart guide
Changed
- Breaking Change:
ssh_docker_tunnel
in thepool_specification
has been replaced by thessh
property.generate_tunnel_script
has been renamed togenerate_docker_tunnel_script
. Please see the configuration doc for more information. streamfile
no longer has an arbitrary max streaming time; the action will stream the file indefinitely until the task completes- Ensure
storage_entity_prefix
is valid and validate container name lengths delpool
action now cleans up and deletes some storage containers immediately afterwards (with confirmation prompts)- Modularized code base
Fixed
- GlusterFS mount ownership/permissions fixed such that SSH users can read/write
- Azure File shared volume setup when invoked from Windows
1.1.0 - 2016-10-05
Added
- Transparent Infiniband assist for SUSE SLES-HPC 12-SP1 image
- Add version for shipyard.py script
- NAMD-GPU, OpenFOAM-Infiniband-IntelMPI, Torch-CPU, Torch-GPU recipes
Changed
- GlusterFS mountpoint is now within
$AZ_BATCH_NODE_SHARED_DIR
so files can be viewed/downloaded with Batch APIs - NAMD-Infiniband-IntelMPI recipe now contains a real Docker image link
Fixed
- GlusterFS not properly starting on Ubuntu
1.0.0 - 2016-09-22
Added
- Automated GlusterFS support
- Added
configdir
argument for convenience in loading configuration files, please see the usage documentation for more details - Ability to retrieve files from live compute nodes in addition to streaming
- Added
filespec
argument for non-interactivestreamfile
andgettaskfile
actions - Added .gitattributes to designate Unix line-endings for text files
- Sample configuration files for each recipe
- Caffe-CPU, OpenFOAM-TCP-OpenMPI, TensorFlow-CPU, TensorFlow-Distributed recipes
Changed
- Updated configuration docs to detail which properties are required vs. those that are optional
- SSH tunnel user is now added with a default expiry time of 7 days which can be modified through the pool configuration file
- Configuration is not output to console by default,
-v
flag added for verbose output - Determinstic remote login settings output (node, ip, port) that can be easily parsed
- Update Azurefile Docker Volume Driver plugin to 0.5.1
Fixed
- Cascade (container-only) start issue with no private registry
- Non-shipyard docker image node prep with new azure-storage package
- Inter-node communication not specified key error on addpool
- Cross-platform fixes:
- Temp file creation used for environment variables
- SSH tunnel creation disabled on Windows if public key is not supplied
- Batch Shipyard Docker container not getting cleaned up if peer-to-peer is disabled
Removed
gpu
:nvidia_driver
:version
property removed from pool configuration and is no longer required as the version is now automatically detected
0.2.0 - 2016-09-08
Added
- Transparent GPU support for Azure N-Series VMs
- New recipes added: Caffe-GPU, CNTK-CPU-OpenMPI, CNTK-GPU-OpenMPI, FFmpeg-GPU, NAMD-Infiniband-IntelMPI, NAMD-TCP, TensorFlow-GPU
Changed
- Multi-instance tasks now automatically complete their job by default. This
removes the need to run the
cleanmijobs
action in the shipyard tool. Please refer to the multi-instance documentation for more information and limitations. - Dumb back-off policy for DHT router convergence
- Optimzed Docker image storage location for Azure VMs
- Prompts added for destructive operations in the shipyard tool
Fixed
- Incorrect file location of node prep finished
- Blocking wait for global resource on pool can now be disabled
- Incorrect process call to query for docker image size when peer-to-peer transfer is disabled
- Use azure-storage 0.33.0 to fix Edm.Int64 overflow issue
0.1.0 - 2016-09-01
Added
- Initial release