Compute Placement API Upgrade Considerations

Bug #1651842 reported by Stephen Gordon on 2016-12-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

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.

It's not entirely clear yet whether this will be a "hard" switch in Ocata, but at the very least it seems it would be prudent to deploy and run the placement stack on Ocata and possibly even stable/newton...

Changed in tripleo:
assignee: nobody → Emilien Macchi (emilienm)
importance: Undecided → High
status: New → In Progress
milestone: none → ocata-3
Changed in tripleo:
assignee: Emilien Macchi (emilienm) → nobody
Changed in tripleo:
milestone: ocata-3 → ocata-rc1
Changed in tripleo:
milestone: ocata-rc1 → ocata-rc2
Changed in tripleo:
milestone: ocata-rc2 → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Emilien Macchi (emilienm) wrote :

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

Changed in tripleo:
status: In Progress → New
status: New → Triaged
Changed in tripleo:
milestone: pike-3 → pike-rc1
Ben Nemec (bnemec) wrote :

This seems to have been an FYI bug for the Ocata release, which has long since shipped. I believe we addressed the placement api upgrade implications so I'm going to close this. If specific issues with the migration come up they should be opened as new bugs.

Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers