516e57bc89
Previously attach_interface tests in project/instances/tests.py did not cover the case of attach_interface by port. This commit adds UT for such cases. Details: - The second call of the mocked network_list_for_tenant retured an empty list. It sounds tricky to change the return value for network_list_for_tenant() in two calls, but this trick was used to skip the processing of port_field_data. This should return a same value for the two calls to test port_field_data() function. - To test the behavior of attach_interface by "port", an unbound port (whose device_owner/device_id of the port is empty) is required, so this commit adds it to neutron_data.py. - test_interface_attach_get() covers a list of choices when "By Port" is selected in the form. - test_interface_attach_post_by_port() is added. Related to the addition of an unbound port to neutron_data.py, the following other tests are adjusted. They assumed that all non-network ports are owned by servers, but it is no longer true as an unbound port is added to the test data. Note that associating an unbound port with a floating IP is a valid operation in neutron, so there is no problem to adjust UTs. - openstack_dashboard/dashboards/project/floating_ips/tests.py - openstack_dashboard/test/unit/api/test_neutron.py Related-Bug: #1943639 Change-Id: Ib0ee342463e5668858078db43c04fe0a1be6e995 |
||
|---|---|---|
| .zuul.d | ||
| doc | ||
| horizon | ||
| openstack_auth | ||
| openstack_dashboard | ||
| playbooks | ||
| releasenotes | ||
| roles | ||
| tools | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .pylintrc | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| babel-django.cfg | ||
| babel-djangojs.cfg | ||
| bindep.txt | ||
| manage.py | ||
| package.json | ||
| plugin-registry.csv | ||
| reno.yaml | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| test-shim.js | ||
| tox.ini | ||
README.rst
Horizon (OpenStack Dashboard)
Horizon is a Django-based project aimed at providing a complete
OpenStack Dashboard along with an extensible framework for building new
dashboards from reusable components. The
openstack_dashboard module is a reference implementation of
a Django site that uses the horizon app to provide
web-based interactions with the various OpenStack projects.
- Project documentation: https://docs.openstack.org/horizon/latest/
- Release management: https://launchpad.net/horizon
- Blueprints and feature specifications: https://blueprints.launchpad.net/horizon
- Issue tracking: https://bugs.launchpad.net/horizon
- Release notes: https://docs.openstack.org/releasenotes/horizon/
Using Horizon
See doc/source/install/index.rst about how to install
Horizon in your OpenStack setup. It describes the example steps and has
pointers for more detailed settings and configurations.
It is also available at Installation Guide.
Getting Started for Developers
doc/source/quickstart.rst or Quickstart
Guide describes how to setup Horizon development environment and
start development.
Building Contributor Documentation
This documentation is written by contributors, for contributors.
The source is maintained in the doc/source directory
using reStructuredText and
built by Sphinx
To build the docs, use:
$ tox -e docsResults are in the doc/build/html directory