metadata service should be setting the objects indirection_api
Bug #1268665 reported by
Nikola Đipanov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Ia12f48227eb238
Changed in nova: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/66520 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=1df6ec71036 380be548d209cd6 58687d25541f6b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1df6ec71036380b e548d209cd65868 7d25541f6b
Author: Nikola Dipanov <email address hidden>
Date: Tue Jan 14 10:02:04 2014 +0100
Set objects indirection API in metadata service
Commit Ia12f48227eb238 0f5da93313cd404 5577d8857c9 introduces objects in
the metadata service.
As metadata service is supposed to be using the objects. baseNovaObject. indirection_ api global to point to the
conductor service for it's database access, we also need to set
nova.
conductor API so that the object actions will be done by RPC to
conductor.
Change-Id: I7aae92c0074e72 841aa6c654ad0ad a25045863b1
Closes-bug: #1268665