Bug #13617

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

Added by Nico C├ęsar about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
06/14/2018
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release:
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

Task #13625: Review 13617-anm-instance-type-loggingClosed

Associated revisions

Revision 4f1e8828
Added by Lucas Di Pentima about 1 year ago

Merge branch '13617-anm-instance-type-logging'
Closes #13617

Arvados-DCO-1.1-Signed-off-by: Lucas Di Pentima <>

History

#1 Updated by Lucas Di Pentima about 1 year ago

  • Assigned To set to Lucas Di Pentima

#2 Updated by Lucas Di Pentima about 1 year ago

  • Status changed from New to In Progress

#3 Updated by Lucas Di Pentima about 1 year ago

  • Target version set to 2018-06-20 Sprint

#4 Updated by Lucas Di Pentima about 1 year ago

Updates at 0275a6282 - branch 13617-anm-instance-type-logging
Test run: https://ci.curoverse.com/job/developer-run-tests/754/

Talked with Nico about using size ids instead of size names when logging, as different instance types can have the same cloud assigned name.

#5 Updated by Peter Amstutz about 1 year ago

Yes, I agree it should definitely be logging the arvados instance type. Does this affect what is returned by the status endpoint as well?

#6 Updated by Lucas Di Pentima about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

#7 Updated by Tom Morris about 1 year ago

  • Release set to 13

Also available in: Atom PDF