Ceilometer using External Endpoint URLs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
In Progress
|
High
|
xingzhou |
Bug Description
I have a working copy of ceilometer up and running (api, collector, and central agent). However, when trying to get my compute agents working properly, I'm running into problems with the Nova endpoint they're trying to use. We have our setup configured so that our compute nodes have no external access, AKA are limited to LAN only.
Unfortunately, Ceilometer seems to grab the publicurl for the Nova endpoint and attempt to use it. Here's an excerpt of the error:
2013-05-06 14:54:52 INFO [urllib3.
2013-05-06 14:54:52 DEBUG [urllib3.
2013-05-06 14:54:53 INFO [urllib3.
2013-05-06 14:54:53 ERROR [ceilometer.
Traceback (most recent call last):
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
search_
File "/usr/lib/
return self._list(
File "/usr/lib/
_resp, body = self.api.
File "/usr/lib/
return self._cs_
File "/usr/lib/
**kwargs)
File "/usr/lib/
resp, body = self.request(url, method, **kwargs)
File "/usr/lib/
**kwargs)
File "/usr/lib/
return session.
File "/usr/lib/
resp = self.send(prep, stream=stream, timeout=timeout, verify=verify, cert=cert, proxies=proxies)
File "/usr/lib/
r = adapter.
File "/usr/lib/
raise ConnectionError
ConnectionError: [Errno 101] ENETUNREACH
I am using Keystone's admin url to authenticate, so that seems to be posting properly (10.x.x.x). However, you can see that it then tries to use X.X.X.X to talk to Nova API.
Changed in ceilometer: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ceilometer: | |
assignee: | nobody → xingzhou (xingzhou) |
I suppose that there should be a config option which identifies whether to use public, internal or admin url for each project that ceilometer polls, am I correct?