openstack/placement
Code Issues Proposed changes
80f585c2d6
placement/placement/direct.py

99 lines
3.9 KiB
Python
Raw Normal View History

Provide a direct interface to placement This is a method of using wsgi-intercept to provide a context manager that allows talking to placement over requests, but without a network. It is a quick and dirty way to talk to and make changes in the placement database where the only network traffic is with the placement database. This is expected to be useful in the creation of tools for performing fast forward upgrades where each compute node may need to "migrate" its resource providers, inventory and allocations in the face of changing representations of hardware (for example pre-existing VGPUs being represented as nested providers) but would like to do so when all non-database services are stopped. A system like this would allow code on the compute node to update the placement database, using well known HTTP interactions, without the placement service being up. The basic idea is that we spin up the WSGI stack with no auth, configured using whatever already loaded CONF we happen to have available. That CONF points to the placement database and all the usual stuff. The context manager provides a keystoneauth1 Adapter class that operates as a client for accessing placement. The full WSGI stack is brought up because we need various bits of middleware to help ensure that policy calls don't explode and so JSON validation is in place. In this model everything else is left up to the caller: constructing the JSON, choosing which URIs to call with what methods (see test_direct for minimal examples that ought to give an idea of what real callers could expect). To make things friendly in the nova context and ease creation of fast forward upgrade tools, SchedulerReportClient is tweaked to take an optional adapter kwarg on construction. If specified, this is used instead of creating one with get_ksa_adapter(), using settings from [placement] conf. Doing things in this way draws a clear line between the placement parts and the nova parts while keeping the nova parts straightforward. NoAuthReportClient is replaced with a base test class, test_report_client.SchedulerReportClientTestBase. This provides an _interceptor() context manager which is a wrapper around PlacementDirect, but instead of producing an Adapter, it produces a SchedulerReportClient (which has been passed the Adapter provided by PlacementDirect). test_resource_tracker and test_report_client are updated accordingly. Caveats to be aware of: * This is (intentionally) set up to circumvent authentication and authorization. If you have access to the necessary database connection string, then you are good to go. That's what we want, right? * CONF construction being left up to the caller is on purpose because right now placement itself is not super flexible in this area and flexibility is desired here. This is not (by a long shot) the only way to do this. Other options include: * Constructing a WSGI environ that has all the necessary bits to allow calling the methods in the handlers directly (as python commands). This would duplicate a fair bit of the middleware and seems error prone, because it's hard to discern what parts of the environ need to be filled. It's also weird for data input: we need to use a BytesIO to pass in data on PUTs and POSTs. * Using either the WSGI environ or wsgi-intercept models but wrap it with a pythonic library that exposes a "pretty" interface to callers. Something like: placement.direct.allocations.update(consumer_uuid, {data}) * Creating a python library that assembles the necessary data for calling the methods in the resource provider objects and exposing that to: a) the callers who want this direct stuff b) the existing handlers in placement (which remain responsible for json manipulation and validation and microversion handling, and marshal data appropriately for the python lib) I've chosen the simplest thing as a starting point because it gives us something to talk over and could solve the immediate problem. If we were to eventually pursue the 4th option, I would hope that we had some significant discussion before doing so as I think it is a) harder than it might seem at first glance, b) likely to lead to many asking "why bother with the http interface at all?". Both require thought. Partially implements blueprint reshape-provider-tree Co-Authored-By: Eric Fried <efried@us.ibm.com> Change-Id: I075785abcd4f4a8e180959daeadf215b9cd175c8
2018-06-05 15:36:14 -07:00
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
"""Call any URI in the placement service directly without real HTTP.
This is useful for those cases where processes wish to manipulate the
Placement datastore but do not want to run Placement as a long running
service. A PlacementDirect context manager is provided. Within that
HTTP requests may be made as normal but they will not actually traverse
a real socket.
"""
Use unittest.mock instead of third party mock Now that we no longer support py27, we can use the standard library unittest.mock module instead of the third party mock lib. Change-Id: I1cffb9710f9e6b9b8b1f5e658d5af8668f3fca4c Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-04-18 11:57:19 -05:00
from unittest import mock
Provide a direct interface to placement This is a method of using wsgi-intercept to provide a context manager that allows talking to placement over requests, but without a network. It is a quick and dirty way to talk to and make changes in the placement database where the only network traffic is with the placement database. This is expected to be useful in the creation of tools for performing fast forward upgrades where each compute node may need to "migrate" its resource providers, inventory and allocations in the face of changing representations of hardware (for example pre-existing VGPUs being represented as nested providers) but would like to do so when all non-database services are stopped. A system like this would allow code on the compute node to update the placement database, using well known HTTP interactions, without the placement service being up. The basic idea is that we spin up the WSGI stack with no auth, configured using whatever already loaded CONF we happen to have available. That CONF points to the placement database and all the usual stuff. The context manager provides a keystoneauth1 Adapter class that operates as a client for accessing placement. The full WSGI stack is brought up because we need various bits of middleware to help ensure that policy calls don't explode and so JSON validation is in place. In this model everything else is left up to the caller: constructing the JSON, choosing which URIs to call with what methods (see test_direct for minimal examples that ought to give an idea of what real callers could expect). To make things friendly in the nova context and ease creation of fast forward upgrade tools, SchedulerReportClient is tweaked to take an optional adapter kwarg on construction. If specified, this is used instead of creating one with get_ksa_adapter(), using settings from [placement] conf. Doing things in this way draws a clear line between the placement parts and the nova parts while keeping the nova parts straightforward. NoAuthReportClient is replaced with a base test class, test_report_client.SchedulerReportClientTestBase. This provides an _interceptor() context manager which is a wrapper around PlacementDirect, but instead of producing an Adapter, it produces a SchedulerReportClient (which has been passed the Adapter provided by PlacementDirect). test_resource_tracker and test_report_client are updated accordingly. Caveats to be aware of: * This is (intentionally) set up to circumvent authentication and authorization. If you have access to the necessary database connection string, then you are good to go. That's what we want, right? * CONF construction being left up to the caller is on purpose because right now placement itself is not super flexible in this area and flexibility is desired here. This is not (by a long shot) the only way to do this. Other options include: * Constructing a WSGI environ that has all the necessary bits to allow calling the methods in the handlers directly (as python commands). This would duplicate a fair bit of the middleware and seems error prone, because it's hard to discern what parts of the environ need to be filled. It's also weird for data input: we need to use a BytesIO to pass in data on PUTs and POSTs. * Using either the WSGI environ or wsgi-intercept models but wrap it with a pythonic library that exposes a "pretty" interface to callers. Something like: placement.direct.allocations.update(consumer_uuid, {data}) * Creating a python library that assembles the necessary data for calling the methods in the resource provider objects and exposing that to: a) the callers who want this direct stuff b) the existing handlers in placement (which remain responsible for json manipulation and validation and microversion handling, and marshal data appropriately for the python lib) I've chosen the simplest thing as a starting point because it gives us something to talk over and could solve the immediate problem. If we were to eventually pursue the 4th option, I would hope that we had some significant discussion before doing so as I think it is a) harder than it might seem at first glance, b) likely to lead to many asking "why bother with the http interface at all?". Both require thought. Partially implements blueprint reshape-provider-tree Co-Authored-By: Eric Fried <efried@us.ibm.com> Change-Id: I075785abcd4f4a8e180959daeadf215b9cd175c8
2018-06-05 15:36:14 -07:00
from keystoneauth1 import adapter
from keystoneauth1 import session
from oslo_utils import uuidutils
import requests
from wsgi_intercept import interceptor
Remove the import pathing for the old structure This commit is the result of running the following search and replace across the project. s/nova\.api\.openstack\.?//g Change-Id: I4974a28de541aace043504f788cf0d100f778cae
2018-08-30 23:07:27 +00:00
from placement import deploy
Provide a direct interface to placement This is a method of using wsgi-intercept to provide a context manager that allows talking to placement over requests, but without a network. It is a quick and dirty way to talk to and make changes in the placement database where the only network traffic is with the placement database. This is expected to be useful in the creation of tools for performing fast forward upgrades where each compute node may need to "migrate" its resource providers, inventory and allocations in the face of changing representations of hardware (for example pre-existing VGPUs being represented as nested providers) but would like to do so when all non-database services are stopped. A system like this would allow code on the compute node to update the placement database, using well known HTTP interactions, without the placement service being up. The basic idea is that we spin up the WSGI stack with no auth, configured using whatever already loaded CONF we happen to have available. That CONF points to the placement database and all the usual stuff. The context manager provides a keystoneauth1 Adapter class that operates as a client for accessing placement. The full WSGI stack is brought up because we need various bits of middleware to help ensure that policy calls don't explode and so JSON validation is in place. In this model everything else is left up to the caller: constructing the JSON, choosing which URIs to call with what methods (see test_direct for minimal examples that ought to give an idea of what real callers could expect). To make things friendly in the nova context and ease creation of fast forward upgrade tools, SchedulerReportClient is tweaked to take an optional adapter kwarg on construction. If specified, this is used instead of creating one with get_ksa_adapter(), using settings from [placement] conf. Doing things in this way draws a clear line between the placement parts and the nova parts while keeping the nova parts straightforward. NoAuthReportClient is replaced with a base test class, test_report_client.SchedulerReportClientTestBase. This provides an _interceptor() context manager which is a wrapper around PlacementDirect, but instead of producing an Adapter, it produces a SchedulerReportClient (which has been passed the Adapter provided by PlacementDirect). test_resource_tracker and test_report_client are updated accordingly. Caveats to be aware of: * This is (intentionally) set up to circumvent authentication and authorization. If you have access to the necessary database connection string, then you are good to go. That's what we want, right? * CONF construction being left up to the caller is on purpose because right now placement itself is not super flexible in this area and flexibility is desired here. This is not (by a long shot) the only way to do this. Other options include: * Constructing a WSGI environ that has all the necessary bits to allow calling the methods in the handlers directly (as python commands). This would duplicate a fair bit of the middleware and seems error prone, because it's hard to discern what parts of the environ need to be filled. It's also weird for data input: we need to use a BytesIO to pass in data on PUTs and POSTs. * Using either the WSGI environ or wsgi-intercept models but wrap it with a pythonic library that exposes a "pretty" interface to callers. Something like: placement.direct.allocations.update(consumer_uuid, {data}) * Creating a python library that assembles the necessary data for calling the methods in the resource provider objects and exposing that to: a) the callers who want this direct stuff b) the existing handlers in placement (which remain responsible for json manipulation and validation and microversion handling, and marshal data appropriately for the python lib) I've chosen the simplest thing as a starting point because it gives us something to talk over and could solve the immediate problem. If we were to eventually pursue the 4th option, I would hope that we had some significant discussion before doing so as I think it is a) harder than it might seem at first glance, b) likely to lead to many asking "why bother with the http interface at all?". Both require thought. Partially implements blueprint reshape-provider-tree Co-Authored-By: Eric Fried <efried@us.ibm.com> Change-Id: I075785abcd4f4a8e180959daeadf215b9cd175c8
2018-06-05 15:36:14 -07:00
class PlacementDirect(interceptor.RequestsInterceptor):
"""Provide access to the placement service without real HTTP.
wsgi-intercept is used to provide a keystoneauth1 Adapter that has access
to an in-process placement service. This provides access to making changes
to the placement database without requiring HTTP over the network - it
remains in-process.
Authentication to the service is turned off; admin access is assumed.
Access is provided via a context manager which is responsible for
turning the wsgi-intercept on and off, and setting and removing
mocks required to keystoneauth1 to work around endpoint discovery.
Example::
with PlacementDirect(cfg.CONF, latest_microversion=True) as client:
allocations = client.get('/allocations/%s' % consumer)
:param conf: An oslo config with the options used to configure
the placement service (notably database connection
string).
:param latest_microversion: If True, API requests will use the latest
microversion if not otherwise specified. If
False (the default), the base microversion is
the default.
"""
def __init__(self, conf, latest_microversion=False):
conf.set_override('auth_strategy', 'noauth2', group='api')
Fix l-c job and move to latest hacking 4.0.0 There are few failure in l-c jobs due to - The conflict is caused by: The user requested pyflakes>=2.1.1 hacking 0.12.0 depends on pyflakes==0.8.1 - The conflict is caused by: The user requested requests>=2.14.2 keystonemiddleware 4.18.0 depends on requests>=2.14.2 oslo-config 6.7.0 depends on requests>=2.18.0 Remove the flake8 and pyflake from lower constraints as they are maintained in hacking side[1]. Maintaining in hacking aas well as in project side can lead to version conflict. Also few more deps from l-c as they are not used in placement directly. Update requests version to 2.25 to fix the http connection failure with 2.18 - https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_dff/766994/6/check/openstack-tox-lower-constraints/dff1943/testr_results.html This commits also moves the code to latest hacking 4.0.0 with W504 in ignore list and fix W503 and other checks. [1] https://github.com/openstack/hacking/blob/4069b0c4f50177dbcaa188aff0de67b4d316a873/lower-constraints.txt#L9 Change-Id: Id2761300060597c1744e76ea77740ed380d98943
2020-12-15 10:16:51 -06:00
def app():
return deploy.loadapp(conf)
Provide a direct interface to placement This is a method of using wsgi-intercept to provide a context manager that allows talking to placement over requests, but without a network. It is a quick and dirty way to talk to and make changes in the placement database where the only network traffic is with the placement database. This is expected to be useful in the creation of tools for performing fast forward upgrades where each compute node may need to "migrate" its resource providers, inventory and allocations in the face of changing representations of hardware (for example pre-existing VGPUs being represented as nested providers) but would like to do so when all non-database services are stopped. A system like this would allow code on the compute node to update the placement database, using well known HTTP interactions, without the placement service being up. The basic idea is that we spin up the WSGI stack with no auth, configured using whatever already loaded CONF we happen to have available. That CONF points to the placement database and all the usual stuff. The context manager provides a keystoneauth1 Adapter class that operates as a client for accessing placement. The full WSGI stack is brought up because we need various bits of middleware to help ensure that policy calls don't explode and so JSON validation is in place. In this model everything else is left up to the caller: constructing the JSON, choosing which URIs to call with what methods (see test_direct for minimal examples that ought to give an idea of what real callers could expect). To make things friendly in the nova context and ease creation of fast forward upgrade tools, SchedulerReportClient is tweaked to take an optional adapter kwarg on construction. If specified, this is used instead of creating one with get_ksa_adapter(), using settings from [placement] conf. Doing things in this way draws a clear line between the placement parts and the nova parts while keeping the nova parts straightforward. NoAuthReportClient is replaced with a base test class, test_report_client.SchedulerReportClientTestBase. This provides an _interceptor() context manager which is a wrapper around PlacementDirect, but instead of producing an Adapter, it produces a SchedulerReportClient (which has been passed the Adapter provided by PlacementDirect). test_resource_tracker and test_report_client are updated accordingly. Caveats to be aware of: * This is (intentionally) set up to circumvent authentication and authorization. If you have access to the necessary database connection string, then you are good to go. That's what we want, right? * CONF construction being left up to the caller is on purpose because right now placement itself is not super flexible in this area and flexibility is desired here. This is not (by a long shot) the only way to do this. Other options include: * Constructing a WSGI environ that has all the necessary bits to allow calling the methods in the handlers directly (as python commands). This would duplicate a fair bit of the middleware and seems error prone, because it's hard to discern what parts of the environ need to be filled. It's also weird for data input: we need to use a BytesIO to pass in data on PUTs and POSTs. * Using either the WSGI environ or wsgi-intercept models but wrap it with a pythonic library that exposes a "pretty" interface to callers. Something like: placement.direct.allocations.update(consumer_uuid, {data}) * Creating a python library that assembles the necessary data for calling the methods in the resource provider objects and exposing that to: a) the callers who want this direct stuff b) the existing handlers in placement (which remain responsible for json manipulation and validation and microversion handling, and marshal data appropriately for the python lib) I've chosen the simplest thing as a starting point because it gives us something to talk over and could solve the immediate problem. If we were to eventually pursue the 4th option, I would hope that we had some significant discussion before doing so as I think it is a) harder than it might seem at first glance, b) likely to lead to many asking "why bother with the http interface at all?". Both require thought. Partially implements blueprint reshape-provider-tree Co-Authored-By: Eric Fried <efried@us.ibm.com> Change-Id: I075785abcd4f4a8e180959daeadf215b9cd175c8
2018-06-05 15:36:14 -07:00
self.url = 'http://%s/placement' % str(uuidutils.generate_uuid())
# Supply our own session so the wsgi-intercept can intercept
# the right thing.
request_session = requests.Session()
headers = {
'x-auth-token': 'admin',
}
# TODO(efried): See below
if latest_microversion:
headers['OpenStack-API-Version'] = 'placement latest'
self.adapter = adapter.Adapter(
session.Session(auth=None, session=request_session,
additional_headers=headers),
Adapter raise_exc=False by default With the exception of a single spot in the code, every request we were making through keystoneauth1 Adapter/Session was using raise_exc=False - i.e. don't raise exceptions on >=400; we process the Response ourselves. As of keystoneauth1 3.9.0 it is possible to pass a raise_exc kwarg into the Adapter upon creation, setting that as the default for all requests on that Adapter. With this patch, we set raise_exc=False on all Adapter creations and only override it in the one spot where we were actually expecting and processing failures as exceptions. Change-Id: I477afdfce746d405adf77134f57670563fd575e1
2018-06-22 09:40:33 -05:00
service_type='placement', raise_exc=False)
Provide a direct interface to placement This is a method of using wsgi-intercept to provide a context manager that allows talking to placement over requests, but without a network. It is a quick and dirty way to talk to and make changes in the placement database where the only network traffic is with the placement database. This is expected to be useful in the creation of tools for performing fast forward upgrades where each compute node may need to "migrate" its resource providers, inventory and allocations in the face of changing representations of hardware (for example pre-existing VGPUs being represented as nested providers) but would like to do so when all non-database services are stopped. A system like this would allow code on the compute node to update the placement database, using well known HTTP interactions, without the placement service being up. The basic idea is that we spin up the WSGI stack with no auth, configured using whatever already loaded CONF we happen to have available. That CONF points to the placement database and all the usual stuff. The context manager provides a keystoneauth1 Adapter class that operates as a client for accessing placement. The full WSGI stack is brought up because we need various bits of middleware to help ensure that policy calls don't explode and so JSON validation is in place. In this model everything else is left up to the caller: constructing the JSON, choosing which URIs to call with what methods (see test_direct for minimal examples that ought to give an idea of what real callers could expect). To make things friendly in the nova context and ease creation of fast forward upgrade tools, SchedulerReportClient is tweaked to take an optional adapter kwarg on construction. If specified, this is used instead of creating one with get_ksa_adapter(), using settings from [placement] conf. Doing things in this way draws a clear line between the placement parts and the nova parts while keeping the nova parts straightforward. NoAuthReportClient is replaced with a base test class, test_report_client.SchedulerReportClientTestBase. This provides an _interceptor() context manager which is a wrapper around PlacementDirect, but instead of producing an Adapter, it produces a SchedulerReportClient (which has been passed the Adapter provided by PlacementDirect). test_resource_tracker and test_report_client are updated accordingly. Caveats to be aware of: * This is (intentionally) set up to circumvent authentication and authorization. If you have access to the necessary database connection string, then you are good to go. That's what we want, right? * CONF construction being left up to the caller is on purpose because right now placement itself is not super flexible in this area and flexibility is desired here. This is not (by a long shot) the only way to do this. Other options include: * Constructing a WSGI environ that has all the necessary bits to allow calling the methods in the handlers directly (as python commands). This would duplicate a fair bit of the middleware and seems error prone, because it's hard to discern what parts of the environ need to be filled. It's also weird for data input: we need to use a BytesIO to pass in data on PUTs and POSTs. * Using either the WSGI environ or wsgi-intercept models but wrap it with a pythonic library that exposes a "pretty" interface to callers. Something like: placement.direct.allocations.update(consumer_uuid, {data}) * Creating a python library that assembles the necessary data for calling the methods in the resource provider objects and exposing that to: a) the callers who want this direct stuff b) the existing handlers in placement (which remain responsible for json manipulation and validation and microversion handling, and marshal data appropriately for the python lib) I've chosen the simplest thing as a starting point because it gives us something to talk over and could solve the immediate problem. If we were to eventually pursue the 4th option, I would hope that we had some significant discussion before doing so as I think it is a) harder than it might seem at first glance, b) likely to lead to many asking "why bother with the http interface at all?". Both require thought. Partially implements blueprint reshape-provider-tree Co-Authored-By: Eric Fried <efried@us.ibm.com> Change-Id: I075785abcd4f4a8e180959daeadf215b9cd175c8
2018-06-05 15:36:14 -07:00
# TODO(efried): Figure out why this isn't working:
# default_microversion='latest' if latest_microversion else None)
self._mocked_endpoint = mock.patch(
Remove pep8 whitespace ignores We had carried over the full list of pep8 whitespace ignores from nova. Trying to address them all in the entire nova repository would have been too big a task; but it's tenable here in placement. Do it now rather than letting these whitespace issues compound. This change removes the E* whitespace ignores and fixes the pep8 issues they were masking. Change-Id: Icbabdb9b56fd5a3e9fd14ab537abf3d0d6456fee
2019-03-01 17:12:20 -06:00
'keystoneauth1.session.Session.get_endpoint',
new=mock.Mock(return_value=self.url))
Provide a direct interface to placement This is a method of using wsgi-intercept to provide a context manager that allows talking to placement over requests, but without a network. It is a quick and dirty way to talk to and make changes in the placement database where the only network traffic is with the placement database. This is expected to be useful in the creation of tools for performing fast forward upgrades where each compute node may need to "migrate" its resource providers, inventory and allocations in the face of changing representations of hardware (for example pre-existing VGPUs being represented as nested providers) but would like to do so when all non-database services are stopped. A system like this would allow code on the compute node to update the placement database, using well known HTTP interactions, without the placement service being up. The basic idea is that we spin up the WSGI stack with no auth, configured using whatever already loaded CONF we happen to have available. That CONF points to the placement database and all the usual stuff. The context manager provides a keystoneauth1 Adapter class that operates as a client for accessing placement. The full WSGI stack is brought up because we need various bits of middleware to help ensure that policy calls don't explode and so JSON validation is in place. In this model everything else is left up to the caller: constructing the JSON, choosing which URIs to call with what methods (see test_direct for minimal examples that ought to give an idea of what real callers could expect). To make things friendly in the nova context and ease creation of fast forward upgrade tools, SchedulerReportClient is tweaked to take an optional adapter kwarg on construction. If specified, this is used instead of creating one with get_ksa_adapter(), using settings from [placement] conf. Doing things in this way draws a clear line between the placement parts and the nova parts while keeping the nova parts straightforward. NoAuthReportClient is replaced with a base test class, test_report_client.SchedulerReportClientTestBase. This provides an _interceptor() context manager which is a wrapper around PlacementDirect, but instead of producing an Adapter, it produces a SchedulerReportClient (which has been passed the Adapter provided by PlacementDirect). test_resource_tracker and test_report_client are updated accordingly. Caveats to be aware of: * This is (intentionally) set up to circumvent authentication and authorization. If you have access to the necessary database connection string, then you are good to go. That's what we want, right? * CONF construction being left up to the caller is on purpose because right now placement itself is not super flexible in this area and flexibility is desired here. This is not (by a long shot) the only way to do this. Other options include: * Constructing a WSGI environ that has all the necessary bits to allow calling the methods in the handlers directly (as python commands). This would duplicate a fair bit of the middleware and seems error prone, because it's hard to discern what parts of the environ need to be filled. It's also weird for data input: we need to use a BytesIO to pass in data on PUTs and POSTs. * Using either the WSGI environ or wsgi-intercept models but wrap it with a pythonic library that exposes a "pretty" interface to callers. Something like: placement.direct.allocations.update(consumer_uuid, {data}) * Creating a python library that assembles the necessary data for calling the methods in the resource provider objects and exposing that to: a) the callers who want this direct stuff b) the existing handlers in placement (which remain responsible for json manipulation and validation and microversion handling, and marshal data appropriately for the python lib) I've chosen the simplest thing as a starting point because it gives us something to talk over and could solve the immediate problem. If we were to eventually pursue the 4th option, I would hope that we had some significant discussion before doing so as I think it is a) harder than it might seem at first glance, b) likely to lead to many asking "why bother with the http interface at all?". Both require thought. Partially implements blueprint reshape-provider-tree Co-Authored-By: Eric Fried <efried@us.ibm.com> Change-Id: I075785abcd4f4a8e180959daeadf215b9cd175c8
2018-06-05 15:36:14 -07:00
super(PlacementDirect, self).__init__(app, url=self.url)
def __enter__(self):
"""Start the wsgi-intercept interceptor and keystone endpoint mock.
A no auth ksa Adapter is provided to the context being managed.
"""
super(PlacementDirect, self).__enter__()
self._mocked_endpoint.start()
return self.adapter
def __exit__(self, *exc):
self._mocked_endpoint.stop()
return super(PlacementDirect, self).__exit__(*exc)
Copy Permalink