I found that the nova-api-* services fail to start on the nova-cloud-controller unit, as haproxy is already bound to the attempted TCP port. Once manually worked around that, another issue surfaced on n-c-c:
It appears to be non-trivial to deploy a working Essex cloud from charms at this point, but I'll confer with the rest of the os charm dev team to determine how deep the essex-functionality rabbit hole could go.
I found that the nova-api-* services fail to start on the nova-cloud- controller unit, as haproxy is already bound to the attempted TCP port. Once manually worked around that, another issue surfaced on n-c-c:
BadRequest: Malformed request url (HTTP 400) (Request-ID: req-9d773c81- 75f0-4dec- ba6e-b11f015ec5 4f) 75f0-4dec- ba6e-b11f015ec5 4f)
ERROR: Malformed request url (HTTP 400) (Request-ID: req-9d773c81-
More detail @ http:// paste.ubuntu. com/10510592/
It appears to be non-trivial to deploy a working Essex cloud from charms at this point, but I'll confer with the rest of the os charm dev team to determine how deep the essex-functionality rabbit hole could go.