New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk size monitoring unexcepted behaviour #2765

Open
feldsam opened this Issue Dec 29, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@feldsam
Contributor

feldsam commented Dec 29, 2018

Description
VM disk size monitored only one time after opennebula service restart using tm/driver/monitor script.

Sat Dec 29 11:24:24 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sat Dec 29 11:24:24 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=4242]
Sat Dec 29 11:25:09 2018 [Z0][InM][D]: Host tst.lin.fedora.host (0) successfully monitored.
Sat Dec 29 11:25:09 2018 [Z0][VMM][D]: VM 97 successfully monitored: STATE=a CPU=0.0 MEMORY=807324 NETRX=6317550576 NETTX=127931671 DISKRDBYTES=285341508 DISKWRBYTES=6207442432 DISKRDIOPS=8641 DISKWRIOPS=15705
Sat Dec 29 11:29:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.

As you see in logs, first time system ds is monitored log is followed by VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=4242], next systems ds monitorings are without VM disk size parsing.

Expected behavior
Disk size monitoring each time system datastore is monitored.

Details

  • Affected Component: Storage
  • Hypervisor: KVM
  • Version: 5.6.2

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@feldsam

This comment has been minimized.

Contributor

feldsam commented Dec 30, 2018

Update:

Looks like, that informations about disk sizes are parsed only every 50 minutes

Sun Dec 30 04:04:25 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 04:54:25 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 05:44:25 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 06:34:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 07:24:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 08:14:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 09:04:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 09:54:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 10:44:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]

system datastore is monitored every 5 minute

Sun Dec 30 04:04:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:04:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:09:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:09:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:14:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:14:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:19:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:19:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:24:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:24:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:29:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:29:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:34:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:34:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:39:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:39:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:44:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:44:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:49:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:49:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:54:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:54:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.

Why? Is there some another option passed to tm_mad/monitor script, which tells if disk_sizes are requested or not? There is some option to configure smaller intervals that actual 50 minutes?

@feldsam

This comment has been minimized.

Contributor

feldsam commented Dec 30, 2018

I found it in code.

//Process VM disk information every 10 monitor actions

feldsam added a commit to FELDSAM-INC/one-addon-3par that referenced this issue Dec 30, 2018

Removed disk size monitoring from todo
Monitoring is working, but opennebula monitors it only every 10 time of datastore monitoring.

Issue opened OpenNebula/one#2765

Signed-off-by: Kristián Feldsam <feldsam@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment