Drop compat for non-update_provider_tree code paths

In Train [1] we deprecated support for compute drivers
that did not implement the update_provider_tree method.
That compat code is now removed along with the get_inventory
method definition and (most) references to it.

As a result there are more things we can remove but those
will come in separate changes.

[1] I1eae47bce08f6292d38e893a2122289bcd6f4b58

Change-Id: Ib62ac0b692eb92a2ed364ec9f486ded05def39ad

1 files changed, 6 insertions, 9 deletions

diff --git a/doc/source/reference/update-provider-tree.rst b/doc/source/reference/update-provider-tree.rst
index e541556a39..ab5419f837 100644
--- a/doc/source/reference/update-provider-tree.rst
+++ b/doc/source/reference/update-provider-tree.rst
@@ -23,13 +23,13 @@ Background
 ----------
 In the movement towards using placement for scheduling and resource management,
 the virt driver method ``get_available_resource`` was initially superseded by
-``get_inventory``, whereby the driver could specify its inventory in terms
-understood by placement. In Queens, a ``get_traits`` driver method was added.
-But ``get_inventory`` is limited to expressing only inventory (not traits or
-aggregates). And both of these methods are limited to the resource provider
-corresponding to the compute node.
+``get_inventory`` (now gone), whereby the driver could specify its inventory in
+terms understood by placement. In Queens, a ``get_traits`` driver method was
+added. But ``get_inventory`` is limited to expressing only inventory (not
+traits or aggregates). And both of these methods are limited to the resource
+provider corresponding to the compute node.
 
-Recent developments such as Nested Resource Providers necessitate the ability
+Developments such as Nested Resource Providers necessitate the ability
 for the virt driver to have deeper control over what the resource tracker
 configures in placement on behalf of the compute node. This need is filled by
 the virt driver method ``update_provider_tree`` and its consumption by the
@@ -130,9 +130,6 @@ aggregates, and traits associated with those resource providers.
             PF1    PF2 PF3   PF4------BW1 (root)
                                  agg2
 
-This method supersedes ``get_inventory`` and ``get_traits``: if this method is
-implemented, neither ``get_inventory`` nor ``get_traits`` is used.
-
 Driver implementations of ``update_provider_tree`` are expected to use public
 ``ProviderTree`` methods to effect changes to the provider tree passed in.
 Some of the methods which may be useful are as follows: