Bug #13617: [a-n-m] labels in instances in AWS are confusing - Arvados

Actions

Copy link

Bug #13617

closed

[a-n-m] labels in instances in AWS are confusing

Added by Nico César almost 6 years ago. Updated almost 6 years ago.

Status:

Resolved

Priority:

Normal

Assigned To:

Lucas Di Pentima

Category:

Target version:

2018-06-20 Sprint

Story points:

Release:

Arvados 1.2

Release relationship:

Auto

Description

since 1.1.4.20180612182441-2 ticket #7478 spot instances show up:

Jun 12 21:13:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:13:13 arvnodeman.jobqueue[11289] INFO: {'real': <NodeSize: id=m4.large, name=Large Instance, ram=8192 disk=0 bandwidth=None price=0.1 driver=Amazon EC2 ...>, 'preemptable': False, 'name': 'Large Instance', 'extra': {'cpu': 2}, 'scratch': 32000, 'price': 0.1, 'ram': 7782, 'bandwidth': None, 'cores': 2, 'disk': 0, 'id': 'm4.large'}
Jun 12 21:13:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:13:13 arvnodeman.jobqueue[11289] INFO: {'real': <NodeSize: id=m4.large, name=Large Instance, ram=8192 disk=0 bandwidth=None price=0.1 driver=Amazon EC2 ...>, 'preemptable': True, 'name': 'Large Instance', 'extra': {'cpu': 2}, 'scratch': 32000, 'price': 0.1, 'ram': 7782, 'bandwidth': None, 'cores': 2, 'disk': 0, 'id': 'm4.large.spot'}

but it's confusing to know in the wishlist which one is being referred:

Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 JobQueueMonitorActor.140593208914768[11289] DEBUG: Calculated wishlist: Large Instance, Large Instance
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Compute Optimized Eight Extra Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Compute Optimized Quadruple Extra Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Compute Optimized Double Extra Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Double Extra Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Compute Optimized Extra Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Extra Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Compute Optimized Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Large Instance: wishlist 0, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0
Jun 12 21:17:13 manage.4xphq.arvadosapi.com env[11286]: 2018-06-12 21:17:13 NodeManagerDaemonActor.e1a8b77a0365[11289] INFO: Large Instance: wishlist 2, up 0 (booting 0, unpaired 0, idle 0, busy 0), down 0, shutdown 0

Subtasks 1 (0 open — 1 closed)