7201c1835f
- Heat GUI part - API wrapper client - API rest endpoint creator (like api/rest/heat) According to above changes, I've fixed all unittest that can work without Heat relevant logic in Horizon. Change-Id: I7b8c61275e1fef9e27a34d7e65693ee00d07110d
40 lines
1.5 KiB
Python
40 lines
1.5 KiB
Python
# Copyright 2012 United States Government as represented by the
|
|
# Administrator of the National Aeronautics and Space Administration.
|
|
# All Rights Reserved.
|
|
#
|
|
# Copyright 2012 Nebula, Inc.
|
|
# Copyright 2013 Big Switch Networks
|
|
#
|
|
# 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.
|
|
|
|
"""
|
|
Methods and interface objects used to interact with external APIs.
|
|
|
|
API method calls return objects that are in many cases objects with
|
|
attributes that are direct maps to the data returned from the API http call.
|
|
Unfortunately, these objects are also often constructed dynamically, making
|
|
it difficult to know what data is available from the API object. Because of
|
|
this, all API calls should wrap their returned object in one defined here,
|
|
using only explicitly defined attributes and/or methods.
|
|
|
|
In other words, Horizon developers not working on openstack_dashboard.api
|
|
shouldn't need to understand the finer details of APIs for
|
|
Keystone/Nova/Glance/Swift et. al.
|
|
"""
|
|
from heat_dashboard.api import heat
|
|
|
|
|
|
__all__ = [
|
|
"heat",
|
|
]
|