Bug #5011

Erroneous monitoring values for EC2 machines

Added by Javi Fontan over 3 years ago. Updated over 3 years ago.

Status:ClosedStart date:02/08/2017
Priority:SponsoredDue date:
Assignee:Javi Fontan% Done:

100%

Category:Drivers - Monitor
Target version:Release 5.4
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.2

Description

The cached values between each cloudwatch call are incorrectly accessed.

Associated revisions

Revision b5cd9190
Added by Sergio Semedi over 3 years ago

B #5011 fixed: ec2 instances monitoring

History

#1 Updated by Javi Fontan over 3 years ago

Also the driver takes a lot of time to gather monitoring info from cloudwatch. Another method to get info in bulk from several VMs should be used or several calls should be parallelized.

#2 Updated by Javi Fontan over 3 years ago

  • Priority changed from Normal to Sponsored

#3 Updated by Sergio Semedi over 3 years ago

  • Status changed from Pending to Assigned
  • Assignee set to Sergio Semedi

#4 Updated by OpenNebula Systems Support Team over 3 years ago

  • Status changed from Assigned to New
  • % Done changed from 0 to 70

#5 Updated by Ruben S. Montero over 3 years ago

  • Assignee changed from Sergio Semedi to Tino Vázquez

#6 Updated by Ruben S. Montero over 3 years ago

  • Assignee changed from Tino Vázquez to Javi Fontan

#7 Updated by Javi Fontan over 3 years ago

  • % Done changed from 70 to 100
  • Resolution set to fixed

#8 Updated by Javi Fontan over 3 years ago

  • Status changed from New to Closed

Also available in: Atom PDF