Project

General

Profile

Actions

Feature #8186

closed

[Node Manager] Support (ephemeral) EBS storage for AWS node types that do not have instance storage, like the M4/C4 classes.

Added by Ward Vandewege over 8 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
1.0

Description

Currently node manager only distinguishes between cloud instance types. Enable the admin to specify the amount of additional storage for specific instance types on AWS.

[Size m4.large]
cores = 2
scratch = 500

Implementation:

Determine how instance storage is available by default for node type. If additional space is needed, attach an EBS device.

This is configured via ex_blockdevicemappings to libcloud create_node() & documented at https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_BlockDeviceMapping.html

Disks should be VolumeType: 'gp2' (General Purpose SSD), have DeleteOnTermination: true, and specify a VolumeSize: that makes up the difference between instance storage (if any) and the required space.

The compute node boot scripts are expected to discover both instance and EBS storage devices and combine them into a single logical partition / file system. In the above example, after boot time configuration the resulting node should have a single 500 GB file system for scratch space.


Subtasks 2 (0 open2 closed)

Task #11853: Ensure that libcloud 0.20.2dev3 is installed on all clustersResolvedNico César06/16/2017Actions
Task #11828: Review 8186-nodemanager-ebsResolvedPeter Amstutz06/14/2017Actions

Related issues

Copied to Arvados - Feature #10183: [Node Manager] Support ephemeral additional storage for Azure node types that do not have sufficient instance storageClosed10/04/2016Actions
Actions

Also available in: Atom PDF