Description of problem:
Nova introduced the placement API service in the 14.0.0 Newton release. This is a separate REST API stack and data model used to track resource provider inventories and usages, along with different classes of resources. For example, a resource provider can be a compute node, a shared storage pool, or an IP allocation pool. The placement service tracks the inventory and usage of each provider. For example, an instance created on a compute node may be a consumer of resources such as RAM and CPU from a compute node resource provider, DISK from an external shared storage pool resource provider and IP addresses from an external IP pool resource provider.
The types of resources consumed are tracked as classes. The service provides a set of standard resource classes but provides the ability to define custom resource classes as needed.
The placement-api service must be deployed at some point after you have upgraded to the 14.0.0 Newton release but before you can upgrade to the 15.0.0 Ocata release. This is so that the resource tracker in the nova-compute service can populate resource provider (compute node) inventory and allocation information which will be used by the nova-scheduler service in Ocata.
Since I've been doing most of the integration work in TripleO, would it make sense to assign the BZ to myself? (I've updated the BZ with the patches in progress).
(In reply to Emilien Macchi from comment #2)
> Since I've been doing most of the integration work in TripleO, would it make
> sense to assign the BZ to myself? (I've updated the BZ with the patches in
For now, yes, question will be ensuring we get Sven or Ollie up to speed on what you have done and how and then ensure test from Compute DFG. I've marked this and the Cells V2 bug as 11.0 blockers and marked them on the DFG sheet as the highest priority items as it seems like we can't release without them...
Assigned to me now, feel free to take over the BZ when needed.
The initial patch series containing the basic placement API service integration in TripleO is well-progressed by Emilien and close to landing.
The outstanding work relates to ensuring the placement API is deployed early enough in the upgrade workflow, so that it has a chance to populate inventories and allocations in advance of the first instance boot that may occur during the rolling upgrade.
I've posted all patches to deploy this service in TripleO. I'm moving this bug to owalsh for the upgrade part that I didn't take care of.
Can this be moved to POST or MODIFIED?
10.0 -> 11.0 upgrade was implemented in OpenStack gerrit 405241
Greenfield install enabled in multiple patches https://review.openstack.org/#/q/topic:tripleo/nova/placement
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.