openstack
/
heat-dashboard
Code Issues Proposed changes

Adds API Access information to Access & Security panel. 

What this does:

  * Makes the Access & Security panel use tabs for each of
    the tables instead of trying to shove them all inline.
  * Adds an "API Access" tab to the above set of tabs.
  * Combines the features of the API Endpoints table, the
    EC2 Credentials download and the OpenRC file download
    into the API Access tab mentioned above.
  * Uses the service "type" instead of "name" in the Endpoints
    table to be nicer about service API abstraction.

Fixes bug 1065671 and fixes bug 1120627.

Change-Id: Iccc65b32d37dc97a96538443cf8c5c08fcea7250
This commit is contained in:
Gabriel Hurley 2013-02-09 14:34:22 -08:00
parent 59425901b2
commit fb784525f9
1 changed files with 0 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
openstack_dashboard/api/__init__.py
View File

@ -1,42 +0,0 @@
# vim: tabstop=4 shiftwidth=4 softtabstop=4
# Copyright 2012 United States Government as represented by the
# Administrator of the National Aeronautics and Space Administration.
# All Rights Reserved.
#
# Copyright 2012 Nebula, Inc.
#
# 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 atributes 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 openstack_dashboard.api import base
from openstack_dashboard.api import cinder
from openstack_dashboard.api import glance
from openstack_dashboard.api import keystone
from openstack_dashboard.api import network
from openstack_dashboard.api import nova
from openstack_dashboard.api import quantum
from openstack_dashboard.api import swift