Mariano Guezuraga
- Email:
- Registered on: 09/22/2014
- Last connection: 12/01/2017
Projects
- OpenNebula (Registered Users, 10/14/2014)
Activity
Reported issues: 6
11/17/2017
- 02:49 PM OpenNebula Revision 3b5a77ec (one): Oned: Fix typo in help (#553)
- (cherry picked from commit fa727a7e13549d83743be4332c3a221761c62556)
- 02:49 PM OpenNebula Revision fa727a7e (one): Oned: Fix typo in help (#553)
10/27/2017
- 11:57 AM OpenNebula Bug #5466: onedb not deleting old_ tables after migration
- I upgraded other installation we have (it holds more VMs/Hosts) and this *didn't* happen:...
10/18/2017
- 01:33 PM OpenNebula Bug #5466: onedb not deleting old_ tables after migration
- As suggested by jfontan on IRC, manually deleting the old_ tables makes fsck happy again
- 01:32 PM OpenNebula Bug #5466 (Pending): onedb not deleting old_ tables after migration
- ...
09/19/2017
- 03:23 PM OpenNebula Backlog #5372: Option to not store monitoring data to the DB
- Actually, it's not only monitoring information, these updates also store the entire VM template, which in our case te...
- 03:17 PM OpenNebula Backlog #5372: Option to not store monitoring data to the DB
- We have other ways to monitor VMs (sending metrics to graphite, for example). Right now we have ~1400 VMs running and...
09/18/2017
- 10:39 AM OpenNebula Backlog #5372: Option to not store monitoring data to the DB
- Thanks for clarifying.
Is there a feature or flag to disable writing VM information back to the DB? (Which is what... - 07:58 AM OpenNebula Backlog #5372 (Pending): Option to not store monitoring data to the DB
- After setting VM_INDIVIDUAL_MONITORING = 'no' and 'VM_MONITORING_EXPIRATION_TIME' = 0 I can see in the database queri...
02/01/2017
- 10:13 AM OpenNebula Bug #5003 (Closed): VMs wrongly reported as ZOMBIES
- ...
Also available in: Atom