diff -Nru manila-ui-2.12.0/CONTRIBUTING.rst manila-ui-2.13.0/CONTRIBUTING.rst --- manila-ui-2.12.0/CONTRIBUTING.rst 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/CONTRIBUTING.rst 2018-01-24 18:58:43.000000000 +0000 @@ -1,16 +1,16 @@ If you would like to contribute to the development of OpenStack, you must follow the steps in this page: - https://docs.openstack.org/infra/manual/developers.html +https://docs.openstack.org/infra/manual/developers.html Once those steps have been completed, changes to OpenStack should be submitted for review via the Gerrit tool, following the workflow documented at: - https://docs.openstack.org/infra/manual/developers.html#development-workflow +https://docs.openstack.org/infra/manual/developers.html#development-workflow Pull requests submitted through GitHub will be ignored. Bugs should be filed on Launchpad, not GitHub: - https://bugs.launchpad.net/manila-ui \ No newline at end of file +https://bugs.launchpad.net/manila-ui diff -Nru manila-ui-2.12.0/debian/changelog manila-ui-2.13.0/debian/changelog --- manila-ui-2.12.0/debian/changelog 2017-12-12 21:35:32.000000000 +0000 +++ manila-ui-2.13.0/debian/changelog 2018-01-26 18:38:00.000000000 +0000 @@ -1,8 +1,15 @@ -manila-ui (2.12.0-0ubuntu1~cloud0) xenial-queens; urgency=medium +manila-ui (2.13.0-0ubuntu1~cloud0) xenial-queens; urgency=medium - * New update for the Ubuntu Cloud Archive. + * New upstream release for the Ubuntu Cloud Archive. - -- Openstack Ubuntu Testing Bot Tue, 12 Dec 2017 21:35:32 +0000 + -- Openstack Ubuntu Testing Bot Fri, 26 Jan 2018 18:38:00 +0000 + +manila-ui (2.13.0-0ubuntu1) bionic; urgency=medium + + * New upstream release for Openstack Queens. + * d/control: Align (Build-)Depends with upstream. + + -- Corey Bryant Fri, 26 Jan 2018 12:27:17 -0500 manila-ui (2.12.0-0ubuntu1) bionic; urgency=medium diff -Nru manila-ui-2.12.0/debian/control manila-ui-2.13.0/debian/control --- manila-ui-2.12.0/debian/control 2017-12-12 14:24:41.000000000 +0000 +++ manila-ui-2.13.0/debian/control 2018-01-26 17:27:17.000000000 +0000 @@ -16,13 +16,13 @@ Build-Depends-Indep: openstack-dashboard (>= 3:13.0.0~b2-0ubuntu2~), python-babel (>= 2.3.4), - python-coverage, + python-coverage (>= 4.0), python-ddt (>= 1.0.1), python-django (>= 1.8), python-django-compressor (>= 2.0), python-django-horizon, python-django-nose (>= 1.4.4), - python-hacking, + python-hacking (>= 0.12.0), python-iso8601 (>= 0.1.11), python-keystoneclient (>= 1:3.8.0), python-manilaclient (>= 1.16.0), @@ -33,10 +33,12 @@ python-nose-exclude, python-openstack.nose-plugin, python-openstackdocstheme (>= 1.17.0), - python-oslo.utils (>= 3.31.0), + python-oslo.utils (>= 3.33.0), python-oslosphinx (>= 4.7.0), python-six (>= 1.10.0), - python-testscenarios, + python-subunit (>= 1.0.0), + python-testrepository (>= 0.0.18), + python-testscenarios (>= 0.4), python-testtools (>= 2.2.0), subunit, testrepository, @@ -55,7 +57,7 @@ python-iso8601 (>= 0.1.11), python-keystoneclient (>= 1:3.8.0), python-manilaclient (>= 1.16.0), - python-oslo.utils (>= 3.31.0), + python-oslo.utils (>= 3.33.0), python-pbr (>= 2.0.0), python-six (>= 1.10.0), ${misc:Depends}, diff -Nru manila-ui-2.12.0/doc/source/admin/index.rst manila-ui-2.13.0/doc/source/admin/index.rst --- manila-ui-2.12.0/doc/source/admin/index.rst 1970-01-01 00:00:00.000000000 +0000 +++ manila-ui-2.13.0/doc/source/admin/index.rst 2018-01-24 18:58:43.000000000 +0000 @@ -0,0 +1,146 @@ +==================== +Administration Guide +==================== + +Shares are file storage that instances can access. Users can +allow or deny a running instance to have access to a share at any time. +For information about using the Dashboard to create and manage shares as +an end user, see the :doc:`User Guide `. + +As an administrative user, you can manage shares and share types for users +in various projects. You can create and delete share types, and view +or delete shares. + +Create a share type +------------------- + +#. Log in to the Dashboard and choose the :guilabel:`admin` + project from the drop-down list. + +#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab + and click the :guilabel:`Shares` category. + +#. Click the :guilabel:`Share Types` tab, and click + :guilabel:`Create Share Type` button. In the + :guilabel:`Create Share Type` window, enter or select the + following values. + + :guilabel:`Name`: Enter a name for the share type. + + :guilabel:`Driver handles share servers`: Choose True or False + + :guilabel:`Extra specs`: To add extra specs, use key=value. + +#. Click :guilabel:`Create Share Type` button to confirm your changes. + +.. note:: + + A message indicates whether the action succeeded. + +Update share type +----------------- + +#. Log in to the Dashboard and choose the :guilabel:`admin` project from + the drop-down list. + +#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab + and click the :guilabel:`Shares` category. + +#. Click the :guilabel:`Share Types` tab, select the share type + that you want to update. + +#. Select :guilabel:`Update Share Type` from Actions. + +#. In the :guilabel:`Update Share Type` window, update extra specs. + + :guilabel:`Extra specs`: To add extra specs, use key=value. + To unset extra specs, use key. + +#. Click :guilabel:`Update Share Type` button to confirm your changes. + +.. note:: + + A message indicates whether the action succeeded. + +Delete share types +------------------ + +When you delete a share type, shares of that type are not deleted. + +#. Log in to the Dashboard and choose the :guilabel:`admin` project from + the drop-down list. + +#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab + and click the :guilabel:`Shares` category. + +#. Click the :guilabel:`Share Types` tab, select the share type + or types that you want to delete. + +#. Click :guilabel:`Delete Share Types` button. + +#. In the :guilabel:`Confirm Delete Share Types` window, click the + :guilabel:`Delete Share Types` button to confirm the action. + +.. note:: + + A message indicates whether the action succeeded. + +Delete shares +------------- + +#. Log in to the Dashboard and choose the :guilabel:`admin` project + from the drop-down list. + +#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab + and click the :guilabel:`Shares` category. + +#. Select the share or shares that you want to delete. + +#. Click :guilabel:`Delete Shares` button. + +#. In the :guilabel:`Confirm Delete Shares` window, click the + :guilabel:`Delete Shares` button to confirm the action. + +.. note:: + + A message indicates whether the action succeeded. + +Delete share server +------------------- + +#. Log in to the Dashboard and choose the :guilabel:`admin` project + from the drop-down list. + +#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab + and click the :guilabel:`Share Servers` category. + +#. Select the share that you want to delete. + +#. Click :guilabel:`Delete Share Server` button. + +#. In the :guilabel:`Confirm Delete Share Server` window, click the + :guilabel:`Delete Share Server` button to confirm the action. + +.. note:: + + A message indicates whether the action succeeded. + +Delete share networks +--------------------- + +#. Log in to the Dashboard and choose the :guilabel:`admin` project + from the drop-down list. + +#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab + and click the :guilabel:`Share Networks` category. + +#. Select the share network or share networks that you want to delete. + +#. Click :guilabel:`Delete Share Networks` button. + +#. In the :guilabel:`Confirm Delete Share Networks` window, click the + :guilabel:`Delete Share Networks` button to confirm the action. + +.. note:: + + A message indicates whether the action succeeded. diff -Nru manila-ui-2.12.0/doc/source/configuration/index.rst manila-ui-2.13.0/doc/source/configuration/index.rst --- manila-ui-2.12.0/doc/source/configuration/index.rst 1970-01-01 00:00:00.000000000 +0000 +++ manila-ui-2.13.0/doc/source/configuration/index.rst 2018-01-24 18:58:43.000000000 +0000 @@ -0,0 +1,33 @@ +============= +Configuration +============= + +It is possible to enable or disable some Manila UI features. To do so, +look for files located in "manila_ui/local/local_settings.d/" directory, +where you can redefine the values of the OPENSTACK_MANILA_FEATURES dict: + +* enable_share_groups +* enable_replication +* enable_migration +* enable_public_share_type_creation +* enable_public_share_group_type_creation +* enable_public_shares +* enabled_share_protocols + +By default, enabled_share_protocols within the OPENSTACK_MANILA_FEATURES +dict contains a list with all the supported protocols. The operator can +change this to display to users only those protocols that has been deployed +and are available to use. E.g. if only NFS is available, the operator is +expected to redefine enabled_share_protocols as follows: + +.. code-block:: python + + OPENSTACK_MANILA_FEATURES = { + 'enable_share_groups': True, + 'enable_replication': True, + 'enable_migration': True, + 'enable_public_share_type_creation': True, + 'enable_public_share_group_type_creation': True, + 'enable_public_shares': True, + 'enabled_share_protocols': ['NFS'], + } diff -Nru manila-ui-2.12.0/doc/source/contributor/features.rst manila-ui-2.13.0/doc/source/contributor/features.rst --- manila-ui-2.12.0/doc/source/contributor/features.rst 1970-01-01 00:00:00.000000000 +0000 +++ manila-ui-2.13.0/doc/source/contributor/features.rst 2018-01-24 18:58:43.000000000 +0000 @@ -0,0 +1,36 @@ +============ +New Features +============ + +When implementing a new feature, you may think about making it optional, +so it could be enabled or disabled in different deployments. + +How to use it: + +.. code-block:: python + + from django.conf import settings + manila_config = getattr(settings, 'OPENSTACK_MANILA_FEATURES', {}) + manila_config.get('your_new_config_option', 'value_of_config_option') + +See :doc:`/configuration/index` section for more configuration details. + +It is also expected that each addition of new logic to Manila UI is covered by +unit tests. + +Test modules should be located under "manila_ui/tests", satisfying +the following template when tests are written for a specific module: + +.. code-block:: none + + manila_ui[/tests]/path/to/[test_]modulename.py + +However, when testing the flow between different modules (using test app), +the tests can be added to a test module that can satisfy +the following template: + +.. code-block:: none + + manila_ui[/tests]/path/to/directory/tests.py + +Manila UI tests use the mock library for testing. diff -Nru manila-ui-2.12.0/doc/source/contributor/index.rst manila-ui-2.13.0/doc/source/contributor/index.rst --- manila-ui-2.12.0/doc/source/contributor/index.rst 1970-01-01 00:00:00.000000000 +0000 +++ manila-ui-2.13.0/doc/source/contributor/index.rst 2018-01-24 18:58:43.000000000 +0000 @@ -0,0 +1,10 @@ +========================= +Contributor Documentation +========================= + +.. toctree:: + :maxdepth: 2 + + contributing + testing + features diff -Nru manila-ui-2.12.0/doc/source/contributor/readme.rst manila-ui-2.13.0/doc/source/contributor/readme.rst --- manila-ui-2.12.0/doc/source/contributor/readme.rst 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/doc/source/contributor/readme.rst 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -.. include:: ../../../README.rst diff -Nru manila-ui-2.12.0/doc/source/contributor/testing.rst manila-ui-2.13.0/doc/source/contributor/testing.rst --- manila-ui-2.12.0/doc/source/contributor/testing.rst 1970-01-01 00:00:00.000000000 +0000 +++ manila-ui-2.13.0/doc/source/contributor/testing.rst 2018-01-24 18:58:43.000000000 +0000 @@ -0,0 +1,43 @@ +======= +Testing +======= + +Starting the app +---------------- + +If everything has gone according to plan, you should be able to run: + +.. code-block:: console + + ./run_tests.sh --runserver 0.0.0.0:8080 + +and have the application start on port 8080. The horizon dashboard will +be located at http://localhost:8080/ + +Running unit tests +------------------ + +The unit tests can be executed directly from within this Manila UI plugin +project directory by using:: + + $ cd ../manila-ui + $ tox + +This is made possible by the dependency in test-requirements.txt upon the +horizon source, which pulls down all of the horizon and openstack_dashboard +modules that the plugin uses. + +To run only py27 unit tests, use following command:: + + $ tox -e py27 + +To run only py34 unit tests, use following command:: + + $ tox -e py34 + +To run unit tests using specific Django version use the following:: + + $ tox -e py27dj17 + $ tox -e py27dj18 + $ tox -e py27dj19 + $ tox -e py27dj110 diff -Nru manila-ui-2.12.0/doc/source/index.rst manila-ui-2.13.0/doc/source/index.rst --- manila-ui-2.12.0/doc/source/index.rst 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/doc/source/index.rst 2018-01-24 18:58:43.000000000 +0000 @@ -3,21 +3,24 @@ You can adapt this file completely to your liking, but it should at least contain the root `toctree` directive. -Welcome to manila-ui's documentation! -===================================== +.. the main title comes from README.rst -Contents: +.. include:: ../../README.rst + +Contents +-------- .. toctree:: :maxdepth: 2 - contributor/readme install/installation - user/usage - contributor/contributing + configuration/index + user/index + admin/index + contributor/index Indices and tables -================== +------------------ * :ref:`genindex` * :ref:`search` diff -Nru manila-ui-2.12.0/doc/source/install/installation.rst manila-ui-2.13.0/doc/source/install/installation.rst --- manila-ui-2.12.0/doc/source/install/installation.rst 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/doc/source/install/installation.rst 2018-01-24 18:58:43.000000000 +0000 @@ -2,11 +2,57 @@ Installation ============ -At the command line:: +Manual Installation +------------------- - $ pip install manila-ui +For Manila UI installation in RDO, see: :ref:`install-rdo`. +For other distributions, begin by +cloning the Horizon and Manila UI repositories:: -Or, if you have virtualenvwrapper installed:: + git clone https://github.com/openstack/horizon + git clone https://github.com/openstack/manila-ui - $ mkvirtualenv manila-ui - $ pip install manila-ui \ No newline at end of file +Create a virtual environment and install Horizon dependencies:: + + cd horizon + python tools/install_venv.py + +Set up your ``local_settings.py`` file:: + + cp openstack_dashboard/local/local_settings.py.example openstack_dashboard/local/local_settings.py + +Open up the copied ``local_settings.py`` file in your preferred text +editor. You will want to customize several settings: + +- ``OPENSTACK_HOST`` should be configured with the hostname of your + OpenStack server. Verify that the ``OPENSTACK_KEYSTONE_URL`` and + ``OPENSTACK_KEYSTONE_DEFAULT_ROLE`` settings are correct for your + environment. (They should be correct unless you modified your + OpenStack server to change them.) + + +Install Manila UI with all dependencies in your virtual environment:: + + tools/with_venv.sh pip install -e ../manila-ui/ + +And enable it in Horizon:: + + cp ../manila-ui/manila_ui/local/enabled/_*.py openstack_dashboard/local/enabled + cp ../manila-ui/manila_ui/local/local_settings.d/_90_manila_*.py openstack_dashboard/local/local_settings.d + +.. _install-rdo: + +Installing Manila UI in RDO +--------------------------- + +In order to install Manila UI in `RDO `__, +please follow the steps below (you may need to use `sudo` privileges +if you are not root):: + +# yum install -y openstack-manila-ui +# systemctl restart httpd +# systemctl restart memcached + +Manila UI will now be available through OpenStack Horizon; look for +the Shares tab under Project > Compute. You can access Horizon with +Manila UI using the same URL and port as before. diff -Nru manila-ui-2.12.0/doc/source/user/index.rst manila-ui-2.13.0/doc/source/user/index.rst --- manila-ui-2.12.0/doc/source/user/index.rst 1970-01-01 00:00:00.000000000 +0000 +++ manila-ui-2.13.0/doc/source/user/index.rst 2018-01-24 18:58:43.000000000 +0000 @@ -0,0 +1,242 @@ +========== +User Guide +========== + +Shares are file storage that you provide access to instances. You can allow +access to a share to a running instance or deny access to a share and allow +access to it to another instance at any time. You can also delete a share. +You can create snapshot from a share if the driver supports it. Only +administrative users can create share types. + +Create a share +-------------- + +#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`. + +#. Click :guilabel:`Create Share`. + + In the dialog box that opens, enter or select the following values. + + :guilabel:`Share Name`: Specify a name for the share. + + :guilabel:`Description`: Optionally, provide a brief description for the + share. + + :guilabel:`Share Type`: Choose a share type. + + :guilabel:`Size (GB)`: The size of the share in gibibytes (GiB). + + :guilabel:`Share Protocol`: Select NFS, CIFS, GlusterFS, or HDFS. + + :guilabel:`Share Network`: Choose a share network. + + :guilabel:`Metadata`: Enter metadata for the share creation if needed. + +#. Click :guilabel:`Create Share`. + +The dashboard shows the share on the :guilabel:`Shares` tab. + +Delete a share +-------------- + +#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`. + +#. Select the check boxes for the shares that you want to delete. + +#. Click :guilabel:`Delete Shares` and confirm your choice. + + A message indicates whether the action was successful. + +Allow access +------------ + +#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`. + +#. Go to the share that you want to allow access and choose + :guilabel:`Manage Rules` from Actions. + +#. Click :guilabel:`Add rule`. + + :guilabel:`Access Type`: Choose ip, user, or cert. + + :guilabel:`Access Level`: Choose read-write or read-only. + + :guilabel:`Access To`: Fill in Access To field. + +#. Click :guilabel:`Add Rule`. + + A message indicates whether the action was successful. + +Deny access +----------- + +#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`. + +#. Go to the share that you want to deny access and choose + :guilabel:`Manage Rules` from Actions. + +#. Choose the rule you want to delete. + +#. Click :guilabel:`Delete rule` and confirm your choice. + + A message indicates whether the action was successful. + +Edit share metadata +------------------- + +#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`. + +#. Go to the share that you want to edit and choose + :guilabel:`Edit Share Metadata` from Actions. + +#. :guilabel:`Metadata`: To add share metadata, use key=value. To unset + metadata, use key. + +#. Click :guilabel:`Edit Share Metadata`. + + A message indicates whether the action was successful. + +Edit share +---------- + +#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`. + +#. Go to the share that you want to edit and choose :guilabel:`Edit Share` from + Actions. + +#. :guilabel:`Share Name`: Enter a new share name. + +#. :guilabel:`Description`: Enter a new description. + +#. Click :guilabel:`Edit Share`. + + A message indicates whether the action was successful. + +Extend share +------------ + +#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`. + +#. Go to the share that you want to edit and choose :guilabel:`Extend Share` + from Actions. + +#. :guilabel:`New Size (GB)`: Enter new size. + +#. Click :guilabel:`Extend Share`. + + A message indicates whether the action was successful. + +Create share network +-------------------- + +#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, + and click :guilabel:`Share Networks`. + +#. Click :guilabel:`Create Share Network`. + + In the dialog box that opens, enter or select the following values. + + :guilabel:`Name`: Specify a name for the share network. + + :guilabel:`Description`: Optionally, provide a brief description for the + share network. + + :guilabel:`Neutron Net`: Choose a neutron network. + + :guilabel:`Neutron Subnet`: Choose a neutron subnet. + +#. Click :guilabel:`Create Share Network`. + +The dashboard shows the share network on the :guilabel:`Share Networks` tab. + +Delete a share network +---------------------- + +#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, and + click :guilabel:`Share Networks`. + +#. Select the check boxes for the share networks that you want to delete. + +#. Click :guilabel:`Delete Share Networks` and confirm your choice. + + A message indicates whether the action was successful. + +Edit share network +------------------ + +#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, and + click :guilabel:`Share Networks`. + +#. Go to the share network that you want to edit and choose + :guilabel:`Edit Share Network` from Actions. + +#. :guilabel:`Name`: Enter a new share network name. + +#. :guilabel:`Description`: Enter a new description. + +#. Click :guilabel:`Edit Share Network`. + + A message indicates whether the action was successful. + +Create security service +----------------------- + +#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, + and click :guilabel:`Security Services`. + +#. Click :guilabel:`Create Security Service`. + + In the dialog box that opens, enter or select the following values. + + :guilabel:`Name`: Specify a name for the security service. + + :guilabel:`DNS IP`: Enter the DNS IP address. + + :guilabel:`Server`: Enter the server name. + + :guilabel:`Domain`: Enter the domain name. + + :guilabel:`User`: Enter the user name. + + :guilabel:`Password`: Enter the password. + + :guilabel:`Confirm Password`: Enter the password again to confirm. + + :guilabel:`Type`: Choose the type from Active Directory, LDAP, or Kerberos. + + :guilabel:`Description`: Optionally, provide a brief description for the + security service. + +#. Click :guilabel:`Create Security Service`. + +The dashboard shows the security service on the :guilabel:`Security Services` +tab. + +Delete a security service +------------------------- + +#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, and + click :guilabel:`Security Services`. + +#. Select the check boxes for the security services that you want to delete. + +#. Click :guilabel:`Delete Security Services` and confirm your choice. + + A message indicates whether the action was successful. + +Edit security service +--------------------- + +#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, + and click :guilabel:`Security Services`. + +#. Go to the security service that you want to edit and choose + :guilabel:`Edit Security Service` from Actions. + +#. :guilabel:`Name`: Enter a new security service name. + +#. :guilabel:`Description`: Enter a new description. + +#. Click :guilabel:`Edit Security Service`. + + A message indicates whether the action was successful. diff -Nru manila-ui-2.12.0/doc/source/user/usage.rst manila-ui-2.13.0/doc/source/user/usage.rst --- manila-ui-2.12.0/doc/source/user/usage.rst 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/doc/source/user/usage.rst 1970-01-01 00:00:00.000000000 +0000 @@ -1,7 +0,0 @@ -===== -Usage -===== - -To use manila-ui in a project:: - - import manila_ui diff -Nru manila-ui-2.12.0/manila_ui/locale/pt_BR/LC_MESSAGES/django.po manila-ui-2.13.0/manila_ui/locale/pt_BR/LC_MESSAGES/django.po --- manila-ui-2.12.0/manila_ui/locale/pt_BR/LC_MESSAGES/django.po 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/manila_ui/locale/pt_BR/LC_MESSAGES/django.po 2018-01-24 18:58:43.000000000 +0000 @@ -1,13 +1,14 @@ # José Mello , 2016. #zanata +# Rodrigo Loures , 2018. #zanata msgid "" msgstr "" -"Project-Id-Version: manila-ui 2.9.1.dev1\n" +"Project-Id-Version: manila-ui VERSION\n" "Report-Msgid-Bugs-To: https://bugs.launchpad.net/openstack-i18n/\n" -"POT-Creation-Date: 2017-06-08 22:16+0000\n" +"POT-Creation-Date: 2018-01-18 10:21+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2016-09-29 08:23+0000\n" +"PO-Revision-Date: 2018-01-23 09:52+0000\n" "Last-Translator: José Mello \n" "Language-Team: Portuguese (Brazil)\n" "Language: pt-BR\n" @@ -417,7 +418,7 @@ msgstr "Salvar Alterações" msgid "Security Services" -msgstr "Serviços de segurança." +msgstr "Serviços de segurança" msgid "Segmentation Id" msgstr "ID de Segmentação" diff -Nru manila-ui-2.12.0/README.rst manila-ui-2.13.0/README.rst --- manila-ui-2.12.0/README.rst 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/README.rst 2018-01-24 18:58:43.000000000 +0000 @@ -1,179 +1,14 @@ -======================== -Team and repository tags -======================== - -.. image:: https://governance.openstack.org/badges/manila-ui.svg - :target: https://governance.openstack.org/reference/tags/index.html - -.. Change things from this point on - -=============================== -manila-ui -=============================== - -Manila Management Dashboard +======================================= +manila-ui - Manila Management Dashboard +======================================= * Free software: Apache license - -.. Uncomment these bullet items when the project is integrated into OpenStack - +* Documentation: https://docs.openstack.org/manila-ui/latest/ * Source: https://git.openstack.org/cgit/openstack/manila-ui * Bugs: https://bugs.launchpad.net/manila-ui +Team and repository tags +------------------------ -Installation instructions -------------------------- - -For Manila UI installation in RDO, see: -`Installing Manila UI in RDO`_. For other distributions, begin by -cloning the Horizon and Manila UI repositories:: - - git clone https://github.com/openstack/horizon - git clone https://github.com/openstack/manila-ui - -Create a virtual environment and install Horizon dependencies:: - - cd horizon - python tools/install_venv.py - -Set up your ``local_settings.py`` file:: - - cp openstack_dashboard/local/local_settings.py.example openstack_dashboard/local/local_settings.py - -Open up the copied ``local_settings.py`` file in your preferred text -editor. You will want to customize several settings: - -- ``OPENSTACK_HOST`` should be configured with the hostname of your - OpenStack server. Verify that the ``OPENSTACK_KEYSTONE_URL`` and - ``OPENSTACK_KEYSTONE_DEFAULT_ROLE`` settings are correct for your - environment. (They should be correct unless you modified your - OpenStack server to change them.) - - -Install Manila UI with all dependencies in your virtual environment:: - - tools/with_venv.sh pip install -e ../manila-ui/ - -And enable it in Horizon:: - - cp ../manila-ui/manila_ui/local/enabled/_*.py openstack_dashboard/local/enabled - cp ../manila-ui/manila_ui/local/local_settings.d/_90_manila_*.py openstack_dashboard/local/local_settings.d - - -Starting the app ----------------- - -If everything has gone according to plan, you should be able to run:: - - ./run_tests.sh --runserver 0.0.0.0:8080 - -and have the application start on port 8080. The horizon dashboard will -be located at http://localhost:8080/ - -Installing Manila UI in RDO ---------------------------- - -In order to install Manila UI in [RDO](https://www.rdoproject.org), -please follow the steps below (you may need to use `sudo` privileges -if you are not root):: - -# yum install -y openstack-manila-ui -# systemctl restart httpd -# systemctl restart memcached - -Manila UI will now be available through OpenStack Horizon; look for -the Shares tab under Project > Compute. You can access Horizon with -Manila UI using the same URL and port as before. - -_`Configuration` ----------------- - -It is possible to enable or disable some Manila UI features. To do so, -look for files located in "manila_ui/local/local_settings.d/" directory, -where you can redefine the values of the OPENSTACK_MANILA_FEATURES dict:: - - * enable_share_groups - * enable_replication - * enable_migration - * enable_public_share_type_creation - * enable_public_share_group_type_creation - * enable_public_shares - * enabled_share_protocols - -By default, enabled_share_protocols within the OPENSTACK_MANILA_FEATURES -dict contains a list with all the supported protocols. The operator can -change this to display to users only those protocols that has been deployed -and are available to use. E.g. if only NFS is available, the operator is -expected to redefine enabled_share_protocols as follows: - -.. code-block:: python - - OPENSTACK_MANILA_FEATURES = { - 'enable_share_groups': True, - 'enable_replication': True, - 'enable_migration': True, - 'enable_public_share_type_creation': True, - 'enable_public_share_group_type_creation': True, - 'enable_public_shares': True, - 'enabled_share_protocols': ['NFS'], - } - -New Features ------------- - -When implementing a new feature, you may think about making it optional, -so it could be enabled or disabled in different deployments. - -How to use it: - -.. code-block:: python - - from django.conf import settings - manila_config = getattr(settings, 'OPENSTACK_MANILA_FEATURES', {}) - manila_config.get('your_new_config_option', 'value_of_config_option') - -See `Configuration`_ section for more configuration details. - -It is also expected that each addition of new logic to Manila UI is covered by -unit tests. - -Test modules should be located under "manila_ui/tests", satisfying -the following template when tests are written for a specific module:: - - manila_ui[/tests]/path/to/[test_]modulename.py - -However, when testing the flow between different modules (using test app), -the tests can be added to a test module that can satisfy -the following template:: - - manila_ui[/tests]/path/to/directory/tests.py - -Manila UI tests use the mock library for testing. - -Running unit tests ------------------- - -The unit tests can be executed directly from within this Manila UI plugin -project directory by using:: - - $ cd ../manila-ui - $ tox - -This is made possible by the dependency in test-requirements.txt upon the -horizon source, which pulls down all of the horizon and openstack_dashboard -modules that the plugin uses. - -To run only py27 unit tests, use following command:: - - $ tox -e py27 - -To run only py34 unit tests, use following command:: - - $ tox -e py34 - -To run unit tests using specific Django version use the following:: - - $ tox -e py27dj17 - $ tox -e py27dj18 - $ tox -e py27dj19 - $ tox -e py27dj110 +.. image:: https://governance.openstack.org/badges/manila-ui.svg + :target: https://governance.openstack.org/reference/tags/index.html diff -Nru manila-ui-2.12.0/requirements.txt manila-ui-2.13.0/requirements.txt --- manila-ui-2.12.0/requirements.txt 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/requirements.txt 2018-01-24 18:58:43.000000000 +0000 @@ -8,7 +8,7 @@ Django<2.0,>=1.8 # BSD django-compressor>=2.0 # MIT iso8601>=0.1.11 # MIT -oslo.utils>=3.31.0 # Apache-2.0 +oslo.utils>=3.33.0 # Apache-2.0 python-keystoneclient>=3.8.0 # Apache-2.0 python-manilaclient>=1.16.0 # Apache-2.0 six>=1.10.0 # MIT diff -Nru manila-ui-2.12.0/test-requirements.txt manila-ui-2.13.0/test-requirements.txt --- manila-ui-2.12.0/test-requirements.txt 2017-11-20 05:47:18.000000000 +0000 +++ manila-ui-2.13.0/test-requirements.txt 2018-01-24 18:58:43.000000000 +0000 @@ -11,7 +11,7 @@ mock>=2.0.0 # BSD mox3>=0.20.0 # Apache-2.0 python-subunit>=1.0.0 # Apache-2.0/BSD -sphinx>=1.6.2 # BSD +sphinx!=1.6.6,>=1.6.2 # BSD openstackdocstheme>=1.17.0 # Apache-2.0 testrepository>=0.0.18 # Apache-2.0/BSD testscenarios>=0.4 # Apache-2.0/BSD