Skip to content
This repository was archived by the owner on Mar 20, 2023. It is now read-only.

Commit 2ad67da

Browse files
committed
Tag for 3.6.0 release
1 parent 342b7fc commit 2ad67da

File tree

4 files changed

+53
-4
lines changed

4 files changed

+53
-4
lines changed

CHANGELOG.md

Lines changed: 50 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,54 @@
22

33
## [Unreleased]
44

5+
## [3.6.0] - 2018-11-06 (SC18 Edition)
6+
### Added
7+
- Kata containers support: run containers on Linux compute nodes with a higher
8+
level of isolation through lightweight VMs. Please see the pool doc for more
9+
information.
10+
- Per-job distributed scratch space support: create on-demand scratch
11+
space shared between tasks of a job which can be particularly useful for MPI
12+
and multi-instance tasks without having to manage a GlusterFS-on-compute
13+
shared data volume. Please see both the pool doc and jobs doc for more
14+
information.
15+
- Add `restrict_default_bind_mounts` option to jobs specifications. This
16+
will restrict automatic host directory bindings to the container filesystem
17+
only to `$AZ_BATCH_TASK_DIR`. This is particularly useful in combination with
18+
container runtimes enforcing VM-level isolation such as Kata containers.
19+
- Allow installation and selection of multiple container runtimes along with
20+
a default container runtime for Docker invocations. Please see the pool doc
21+
for more information under `container_runtimes`.
22+
- Support for Standard SSD and Ultra SSD managed disks for RemoteFS clusters.
23+
In conjunction with this change, Availability Zone support has been added
24+
for manage disks and storage cluster VMs. Please see the relevant
25+
documentation for more information.
26+
27+
### Changed
28+
- **Breaking Change:** the `premium` property under `remote_fs`:`managed_disks`
29+
has been replaced with `sku`. Please see the RemoteFS configuration doc for
30+
more information.
31+
- **Breaking Change:** the Singularity container runtime is no longer installed
32+
by default, please see the pool doc to configure pools to install Singularity
33+
as needed under `container_runtimes`:`install`.
34+
- Renamed MADL recipe to HPMLA
35+
- Updated NC/ND driver to 410.72 with CUDA 10 support
36+
- Updated blobxfer to 1.5.4
37+
- Updated LIS, Prometheus, and Grafana
38+
- Updated other dependencies to latest
39+
- Updated binary builds and Windows Docker images to Python 3.7.1
40+
41+
### Fixed
42+
- `input_data` utilizing Azure File shares ([#243](https://github.com/Azure/batch-shipyard/issues/243))
43+
- New NV driver location ([#244](https://github.com/Azure/batch-shipyard/issues/244))
44+
- Fixed non-public Azure region AAD login issues
45+
- Fixed Singularity image download issues
46+
- Fixed Grafana update regression with default Batch Shipayrd Dashboard
47+
- Fixed SSH login to monitoring resource after federation feature merge
48+
- Enable Singularity on Ubuntu 18.04
49+
50+
### Removed
51+
- Debian 8 host support
52+
553
## [3.6.0b1] - 2018-09-20
654
### Added
755
- Task and node count commands: `jobs tasks counts` and `pool nodes counts`
@@ -1413,7 +1461,8 @@ transfer is disabled
14131461
#### Added
14141462
- Initial release
14151463

1416-
[Unreleased]: https://github.com/Azure/batch-shipyard/compare/3.6.0b1...HEAD
1464+
[Unreleased]: https://github.com/Azure/batch-shipyard/compare/3.6.0...HEAD
1465+
[3.6.0]: https://github.com/Azure/batch-shipyard/compare/3.6.0b1...3.6.0
14171466
[3.6.0b1]: https://github.com/Azure/batch-shipyard/compare/3.6.0a1...3.6.0b1
14181467
[3.6.0a1]: https://github.com/Azure/batch-shipyard/compare/3.5.3...3.6.0a1
14191468
[3.5.3]: https://github.com/Azure/batch-shipyard/compare/3.5.2...3.5.3

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
[![Image Layers](https://images.microbadger.com/badges/image/alfpark/batch-shipyard:latest-cli.svg)](http://microbadger.com/images/alfpark/batch-shipyard)
66

77
# Batch Shipyard
8-
<img src="https://azurebatchshipyard.blob.core.windows.net/github/README-dash.png" alt="dashboard" width="1024" />
8+
<img src="https://azurebatchshipyard.blob.core.windows.net/github/README-dash.gif" alt="dashboard" width="1024" />
99

1010
[Batch Shipyard](https://github.com/Azure/batch-shipyard) is a tool to help
1111
provision, execute, and monitor container-based batch processing and HPC

convoy/version.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@
2222
# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
2323
# DEALINGS IN THE SOFTWARE.
2424

25-
__version__ = '3.6.0b1'
25+
__version__ = '3.6.0'

docs/66-batch-shipyard-resource-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
The focus of this article is to explain how to provision a resource monitor
33
for monitoring Batch pools and RemoteFS clusters.
44

5-
<img src="https://azurebatchshipyard.blob.core.windows.net/github/66-container_metrics.png" alt="dashboard" width="1024" />
5+
<img src="https://azurebatchshipyard.blob.core.windows.net/github/README-dash.gif" alt="dashboard" width="1024" />
66

77
## Overview
88
For many scenarios, it is often desirable to have visibility into a set of

0 commit comments

Comments
 (0)