improve how xenapi RRD records are retrieved
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| OpenStack Compute (nova) |
Undecided
|
Armando Migliaccio |
Bug Description
There is nothing particularly wrong with how RRD records are retrieved in xenapi today.
However there are a couple of potential issues, as described below:
- RRD XMLs are always obtained using http over the XS management interface address. Albeit this is fine in most cases there are problems when: i) nova-compute domU is talking to xapi using the internal management network (e.g. talking to xapi via 169.254.0.1) and traffic cannot be routed between domU and dom0; ii) in resource pools, the host address from the xenapi session handle is always the master, which could get overloaded if there are too many requests.
- get_rrd and get_rrd_updates could politely log the IOError exceptions.
I propose to use FLAGS.xenapi_
- we transparently use the appropriate scheme and server (regardless of whether the host is in a pool or not).
- it is quicker (we don't need to call xapi to get the address)
Changed in nova: | |
assignee: | nobody → Armando Migliaccio (armando-migliaccio) |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
description: | updated |
description: | updated |
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 00c77e0e9af6ae1
Author: Armando Migliaccio <email address hidden>
Date: Mon Feb 13 18:46:57 2012 +0000
bug 931604: improve how xenapi RRD records are retrieved
switch to using FLAGS.xenapi_
address to talk to in order to fetch RRD XMLs. See bug report for
more info.
Change-Id: Iad6520cdb15f32
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → essex-4 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
Fix proposed to branch: master /review. openstack. org/4072
Review: https:/